I read "Metadata files are not required to have additional metadata columns, so a file containing only an ID column is a valid QIIME 2 metadata file" and thought it would make my run work just fine. I even spent time validating the single column metadata file was correct. Then added the numeric column (still go the error as it was removed, leaving only the 'valid' single column of IDs), then finally got to the idea of making the column non-numeric (prepended a character to the numbers). I think it could be a lot more clear if someone is trying to run with a metadata file that is very barebones.
I changed the documentation but it might be best to actually have a metadata test with proper feedback (e.g. "ERROR: no proper column with non-numeric, non-unique entries found"). That is for another time though.
Description of the bug
The description "Metadata files are not required to have additional metadata columns" in https://nf-co.re/ampliseq/dev/parameters#metadata is wrong. Report in nf-core clack channel ampliseq:
Command used and terminal output
No response
Relevant files
No response
System information
No response