[Feature Request]: DSP input parameter groupings, rendering order

[yuanchi2807]

Feature description

Pipeline input parameters are rendered in alphabetical order today.
User experience would improve to divide them into mandatory, optional fields to accomodate general and expert users.
General users only need to fill in the mandatory section, where optional fields allow experts to further configure a pipeline.

Describe alternatives you've considered

No response

Anything else?

No response

[andrewballantyne]

@yuanchi2807 I'm fairly certain (looking at the code) we just render them in order they are in the params section... have you tried reordering your params to see if it reorders?

[yuanchi2807]

@andrewballantyne
We put in

    name: str = "LLM-pipeline",  # name of Ray cluster
    min_worker: int = 2,  # min number of workers
    max_worker: int = 2,  # max number of workers
    cluster_up_tmout: int = 5,  # minutes to wait for the Ray cluster achived min_worker number
    wait_cluster_ready_tmout: int = 0,  # seconds to wait for Ray cluster to become available
    wait_cluster_nodes_ready_tmout: int = 1,  # seconds to wait for cluster nodes to be ready
    ....

and the Pipeline input parameters section begins like this.

[andrewballantyne]

Ooooh, most interesting. Thanks for the additional information @yuanchi2807

I am going to pull in some backend/notebook help to understand what is happening here. cc @harshad16 @HumairAK

If things are all generated by Kubeflow & the SDK -- is there anyway for them to order the items? Because it seems the params might sort them on that side of things (either in Elyra or in some other fashion).

[roytman]

@andrewballantyne , you're right. It is done by the compiler, I see the input parameters according ABC in the yaml file.
e.g.

  - name: execute-ray-jobs
      params:
      - name: checkpoint_path
        value: $(params.checkpoint_path)
      - name: cos_access_secret
        value: $(params.cos_access_secret)
      - name: http_retries
        value: $(params.http_retries)
      - name: init-notifier-output
        value: $(tasks.init-notifier.results.output)
      - name: input_path
        value: $(params.input_path)
      - name: output_path
        value: $(params.output_path)
      - name: script_name
        value: $(params.script_name)
      - name: start-ray-cluster-output
        value: $(tasks.start-ray-cluster.results.output)
      - name: switch
        value: $(params.switch)
      - name: wait_job_ready_retries
        value: $(params.wait_job_ready_retries)
      - name: wait_job_ready_tmout
        value: $(params.wait_job_ready_tmout)
      - name: wait_print_tmout
        value: $(params.wait_print_tmout)
        ```

[andrewballantyne]

If there is metadata you can get on the run -- we could sort them optionally based on that.

[DaoDaoNoCode]

cc @yannnz