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
Hello, as I reported into the #ampliseq Slack thread here, https://nfcore.slack.com/archives/CEA7TBJGJ/p1736280240867139, the nf-core/ampliseq usage page is misleading naive users like me. It is no longer possible to use dashes (-) in sample IDs but, under the metadata section, we can read this: 'Sample identifiers should be 36 characters long or less, and also contain only ASCII alphanumeric characters (i.e. in the range of [a-z], [A-Z], or [0-9]), or the dash (-) character. '.
Could you please update this? It would be useful to add it to the Sample sheet input section as well, please.
I also didn't find it too clear whether users can use the underscore (which, we can), so that may be an improvement to the usage page as well.
Adding it to the error message ouput within the command line would be useful as well.
It's just that dashes were allowed before so users returning after a while could fall into this rookie trap (laughing).
Thank you !
Command used and terminal output
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
Hello, as I reported into the #ampliseq Slack thread here, https://nfcore.slack.com/archives/CEA7TBJGJ/p1736280240867139, the nf-core/ampliseq usage page is misleading naive users like me. It is no longer possible to use dashes (-) in sample IDs but, under the metadata section, we can read this: 'Sample identifiers should be 36 characters long or less, and also contain only ASCII alphanumeric characters (i.e. in the range of [a-z], [A-Z], or [0-9]), or the dash (-) character. '.
Could you please update this? It would be useful to add it to the Sample sheet input section as well, please.
I also didn't find it too clear whether users can use the underscore (which, we can), so that may be an improvement to the usage page as well.
Adding it to the error message ouput within the command line would be useful as well.
It's just that dashes were allowed before so users returning after a while could fall into this rookie trap (laughing).
Thank you !
Command used and terminal output
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: