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 was running the nascent pipeline v2.1.1 (v2.2.0 didn't work due to #) for two runs of the same sample.
I encountered an error at the step of samtools sort:
[51/e45e94] Submitted process > NFCORE_NASCENT:NASCENT:ALIGN_BWA:BAM_SORT_STATS_SAMTOOLS:SAMTOOLS_SORT (EXP_T1)
Pulling Singularity image https://depot.galaxyproject.org/singularity/mulled-v2-008daec56b7aaf3f162d7866758142b9f889d690:e8a286b2e789c091bac0a57302cdc78aa0112353-0 [cache /resources/containers/depot.galaxyproject.org-singularity-mulled-v2-008daec56b7aaf3f162d7866758142b9f889d690-e8a286b2e789c091bac0a57302cdc78aa0112353-0.img]
ERROR ~ fromIndex = -1
-- Check script '/users/dmitry.mylarshchikov/.nextflow/assets/nf-core/nascent/./workflows/nascent.nf' at line: 222 or see '.nextflow.log' file for more details
[5a/85327c] Submitted process > NFCORE_NASCENT:NASCENT:ALIGN_BWA:BAM_SORT_STATS_SAMTOOLS:SAMTOOLS_INDEX (EXP_T1)
I checked out #113, but solution was not applicable to my case. By trying different things, I found out that the reason is in the sample name. Initially, I put a name EXP, and it failed. I put a longer name, DUTTKE and it failed again. But it is running now fine with sample name DUTTKE_REP1.
So, apparently, v2.1.1 requires sample names to have at least one underscore. I cannot test it on v2.2.0 due to another bug, but could you please add this info to the docs?
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
Hey!
I was running the nascent pipeline v2.1.1 (v2.2.0 didn't work due to #) for two runs of the same sample.
I encountered an error at the step of
samtools sort
:I checked out #113, but solution was not applicable to my case. By trying different things, I found out that the reason is in the sample name. Initially, I put a name
EXP
, and it failed. I put a longer name,DUTTKE
and it failed again. But it is running now fine with sample nameDUTTKE_REP1
.So, apparently, v2.1.1 requires sample names to have at least one underscore. I cannot test it on v2.2.0 due to another bug, but could you please add this info to the docs?
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: