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
Is your feature request related to a problem? Please describe.
Currently, to set a title for IGV track we use field name. In case of applying this plugin for an array of files, hardcoded in name value is used for all added tracks making it impossible to identify which file is displayed.
Additional context
We should take into account that users, by mistake, can assign to name values from input or output of not appropriate type or size. The appropriate type should be string or string[] of the same size as array of files to be visualized in IGV. If any error occurs, the default value (output id) should be used.
The text was updated successfully, but these errors were encountered:
Yep, if the input has upstream set as 'sd:upstreamSource': "first_biological_condition/alias" for example, we will get value from the alias of the upstream experiment
Is your feature request related to a problem? Please describe.
Currently, to set a title for IGV track we use field
name
. In case of applying this plugin for an array of files, hardcoded inname
value is used for all added tracks making it impossible to identify which file is displayed.Describe the solution you'd like
Being able to set
name
from the workflow inputs or outputs would allow us to have proper names for IGV tracks.Additional context
We should take into account that users, by mistake, can assign to
name
values from input or output of not appropriate type or size. The appropriate type should bestring
orstring[]
of the same size as array of files to be visualized in IGV. If any error occurs, the default value (output id) should be used.The text was updated successfully, but these errors were encountered: