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
I'm using a sample sheet in dorado (v0.9.0) to demux a run, and then feeding it into wf-16s. It's giving me a nonsensical fastcat error:
ERROR ~ Error executing process > 'fastcat (1)'
Caused by:
Process `fastcat (1)` terminated with an error exit status (1)
Command executed:
mkdir fastcat_stats
mkdir fastq_chunks
# Save file as compressed fastq
fastcat -s barcode001 -f fastcat_stats/per-file-stats.tsv -i fastcat_stats/per-file-runids.tsv -l fastcat_stats/per-file-basecallers.tsv --histograms histograms <(
samtools cat -b <(find . -name 'input_src*') | samtools fastq - -n -T '*' -o - -0 -
) | if [ "0" = "0" ]; then
bgzip -@ 4 > fastq_chunks/seqs.fastq.gz
else
split -l null -d --additional-suffix=.fastq.gz --filter='bgzip -@ 4 > $FILE' - fastq_chunks/seqs_;
fi
mv histograms/* fastcat_stats
# get n_seqs from per-file stats - need to sum them up
awk 'NR==1{for (i=1; i<=NF; i++) {ix[$i] = i}} NR>1 {c+=$ix["n_seqs"]} END{print c}' fastcat_stats/per-file-stats.tsv > fastcat_stats/n_seqs
# get unique run IDs (we add `-F '\t'` as `awk` uses any stretch of whitespace
# as field delimiter per default and thus ignores empty columns)
awk -F '\t' '
NR==1 {for (i=1; i<=NF; i++) {ix[$i] = i}}
# only print run_id if present
NR>1 && $ix["run_id"] != "" {print $ix["run_id"]}
' fastcat_stats/per-file-runids.tsv | sort | uniq > fastcat_stats/run_ids
# get unique basecall models
awk -F '\t' '
NR==1 {for (i=1; i<=NF; i++) {ix[$i] = i}}
# only print basecall model if present
NR>1 && $ix["basecaller"] != "" {print $ix["basecaller"]}
' fastcat_stats/per-file-basecallers.tsv | sort | uniq > fastcat_stats/basecallers
Command exit status:
1
Command output:
(empty)
Command error:
**ERROR: Read's barcode number (2609) is greater than MAX_BARCODES (1025)**
Work dir:
/mnt/ix1/Projects/M103_250118_nanopore16S/nextflow/work/5f/1e0e25c7d320b953140ae0430068f7
Container:
/mnt/ix1/Projects/M103_250118_nanopore16S/nextflow/work/singularity/ontresearch-wf-common-shabadd33adae761be6f2d59c6ecfb44b19cf472cfc.img
Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`
The barcode number that it's referencing is not an actual barcode number but the last four digits of our sample ID (eg. PNNNN_NNNNN). At first I thought it was because fastcat is getting confused because of my directory structure (eg samples/reads.bam for wf-16s), or that its soft link had that identifier in there. But after eliminating all of those options, I discovered that the culprit is:
Dorado was using the sample sheet to replace the barcode with the alias in the BC tag field, but this confuses fastcat. Rerunning dorado demux without a sample sheet fixes the issue.
The text was updated successfully, but these errors were encountered:
I think this will need to be raised internally as an issue in dorado as it should not be mixing up the barcode name and the barcode alias fields; the items should remain distinct.
Could you possibly share a snippet of the file you are inputting into the workflow around the region of this read? Along with an illustration of the directory layout you have.
I'm using a sample sheet in dorado (v0.9.0) to demux a run, and then feeding it into wf-16s. It's giving me a nonsensical fastcat error:
The barcode number that it's referencing is not an actual barcode number but the last four digits of our sample ID (eg. PNNNN_NNNNN). At first I thought it was because fastcat is getting confused because of my directory structure (eg samples/reads.bam for wf-16s), or that its soft link had that identifier in there. But after eliminating all of those options, I discovered that the culprit is:
Dorado was using the sample sheet to replace the barcode with the alias in the BC tag field, but this confuses fastcat. Rerunning dorado demux without a sample sheet fixes the issue.
The text was updated successfully, but these errors were encountered: