You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I pass a data collection parameter of collection_typepaired - a dataset pair - it will just run one job and produce an output. If I pass it a list of paired datasets - a very different operation occurs - it will map over the inputs and produced outputs collected together. Yet the web UI just lists these options together in the same select box and doesn't provide any indication even after being selected that a very different thing is going to occur.
The distinction should mirror that of datasets IMO (as it used to) - passing a paired parameter a list:paired input is very much like passing a data parameter a list input - and the UI should be similar. But even if I'm overruled and there is a desire to stick it all in one drop down - there should be some visual indication somehow made.
If I pass a data collection parameter of
collection_type
paired
- a dataset pair - it will just run one job and produce an output. If I pass it a list of paired datasets - a very different operation occurs - it will map over the inputs and produced outputs collected together. Yet the web UI just lists these options together in the same select box and doesn't provide any indication even after being selected that a very different thing is going to occur.The distinction should mirror that of datasets IMO (as it used to) - passing a
paired
parameter alist:paired
input is very much like passing adata
parameter alist
input - and the UI should be similar. But even if I'm overruled and there is a desire to stick it all in one drop down - there should be some visual indication somehow made.What are your thoughts @guerler?
The text was updated successfully, but these errors were encountered: