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
Many tools have the genome select list propagated where the first in the list is automatically selected by default.
It would avoid a common usage error (user doesn't change the genome) to have the first "entry" in the list state "Select database" or something else similar. Then trap the required missing database selection at job submission (model after existing required field warnings).
Even if we just modified mapping tools, the majority of reported usage issues due to genome form-entry mistakes would be avoided. Examples: BWA/BWA-MEM, Bowtie2, HISAT2
Update: Featurecounts modified to require active selection or tool form will not submit. Great! Testing at usegalaxy.org with updated tool v 1.6.0.3 galaxyproject/usegalaxy-playbook#52
Many tools have the genome select list propagated where the first in the list is automatically selected by default.
It would avoid a common usage error (user doesn't change the genome) to have the first "entry" in the list state "Select database" or something else similar. Then trap the required missing database selection at job submission (model after existing required field warnings).
Even if we just modified mapping tools, the majority of reported usage issues due to genome form-entry mistakes would be avoided. Examples: BWA/BWA-MEM, Bowtie2, HISAT2
Update: recent examples
The text was updated successfully, but these errors were encountered: