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
Actual submission script: /hot/user/alfgonzalez/project/project-LAND-SARC/project-SARC-LAND/pipeline/TCGA-STSA/metapipeline-DNA-5.0.0-rc.4/input/launch_TCGA-STSA_WXS_meta.sh
Expected behavior
Gets through align-dna with no issue but gets lost in call-gSNP
Screenshots
Additional context
Name of the output file from aling-DNA: BWA-MEM2-2.2.1_TCGA-STSA_TCGASTSA000001-N001-B01-P
Metapipeline-DNA input sample name: TCGASTSA000001-N001-B01-P
The text was updated successfully, but these errors were encountered:
Would it be as simple as doing any one of the following? :
Rename the output of align-DNA to eliminate underscores?
Renaming sm tag in the call-snp input.csv generation? https://github.com/uclahs-cds/metapipeline-DNA/blob/main/module/call_gSNP/create_CSV_call_gSNP.nf#L81-L89
Describe the issue
Metapipeline erros out because file can't be found in call-gSNP step
*Submission script
/hot/user/alfgonzalez/project/project-LAND-SARC/project-SARC-LAND/pipeline/TCGA-STSA/metapipeline-DNA-5.0.0-rc.4/input/launch_TCGA-STSA_WXS_meta.sh
/hot/user/alfgonzalez/project/project-LAND-SARC/project-SARC-LAND/pipeline/TCGA-STSA/metapipeline-DNA-5.0.0-rc.4/input/test_TCGA-STSA_WXS_meta.input.config
/hot/project/disease/SarcomaTumor/SARC-000118-SarcomaLandscape/data/TCGA-STSA/metapipeline-DNA-5.0.0-rc.4/leading_work_dir
/hot/project/disease/SarcomaTumor/SARC-000118-SarcomaLandscape/data/TCGA-STSA/metapipeline-DNA-5.0.0-rc.4/leading_work_dir/1f/f500711d12b1718166b3b79cc040d1/.command.log
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Gets through align-dna with no issue but gets lost in call-gSNP
Screenshots
Additional context
Name of the output file from aling-DNA:
BWA-MEM2-2.2.1_TCGA-STSA_TCGASTSA000001-N001-B01-P
Metapipeline-DNA input sample name:
TCGASTSA000001-N001-B01-P
The text was updated successfully, but these errors were encountered: