Mehrdad Jaberi
05/13/2025, 4:40 PM--user-orfs-faa and --user-orfs-gff and mistakenly defined --orf-caller.
I see in the working directory, the .command.sh for the process NFCORE_METATDENOVO:METATDENOVO:KOFAMSCAN:KOFAMSCAN_SCAN used the correct input:
exec_annotation \
--profile profiles \
--ko-list ko_list \
--format detail-tsv \
--cpu 6 \
XXXXX.okay.aa \
-o kofamscan_output.tsv
but in the results directory the naming is:
results/kofamscan/sample_XXX.transdecoder.kofamscan_output.tsv.gz
I guess it is a naming issue??
I mean "transdecoder" has nothing to do with this output! rightDaniel Lundin
05/14/2025, 4:49 AM--orf-caller to transdecoder? I'm not sure what would happen in this case, was transdecoder invoked?Mehrdad Jaberi
05/14/2025, 8:33 AMorf-caller so its value was not null but transdecoder.
I believe in this case, the file names are wrong. Maybe there should be a checkpoint either orf-caller or user-orfs-name to be used.
need a bug?
thanks.Daniel Lundin
05/14/2025, 8:39 AMorf_caller doesn't have a default in the current version (but the docs say differently). Which version did you run?Mehrdad Jaberi
05/14/2025, 8:39 AMdevMehrdad Jaberi
05/14/2025, 8:40 AMorf-caller and the output files are correctly named.Daniel Lundin
05/14/2025, 8:40 AMuser_orfs in their names, unless you set --user_orfs_name to something else.Daniel Lundin
05/14/2025, 8:41 AMDaniel Lundin
05/14/2025, 8:43 AMsummary_tables directory, so this is what I automatically check. I might hence, again, miss naming in the other output directories.