Closed mortunco closed 8 years ago
Tunc; Sorry about the problem. It looks like the ensemble process finished okay and you're at the stage of creating GEMINI databases. If you don't need these, you can turn off gemini in the algorithm section of your samples (http://bcbio-nextgen.readthedocs.org/en/latest/contents/configuration.html#post-processing):
algorithm:
tools_off: [gemini]
Hopefully that'll finish the processing cleanly.
Regarding the underlying error, it looks like something is problematic about the created ensemble file. The informative error is:
Number of columns at 1:65745 does not match the number of samples (2 vs 4).
If you look at the ensemble file (/mnt/work/gemini/ICGC-ensemble.vcf.gz
), is there anything wrong with this position (chromosome 1, position 65745). If this is the same configuration as previously it seems like you should have 2 samples (tumor/normal) but instead have 4 so something is off there.
Hope this helps with finishing and debugging if you want to look at it more. Thanks for all your patience getting this running.
Dear Brad;
Thank you for the explanation. I am trying to figure out that sample problem. Also,
About my input file is; So there are two samples. Just a quick conformation, I have my bam indexes in my input folder in s3. Do you think it might be related with that problem ? Although I am sure about those indexes are always asked, can this last step be originated from this thing?
ubuntu@frontend001:/encrypted/project10/work/inputs/tuncproject/icgcrun/input$ ls
normal.bam tumor.bam tx
I checked that specific location and I couldn't understand if there is info. What should I be seeing as an error ?
ubuntu@frontend001:/encrypted/project10/work/ensemble$ cat ICGC-ensemble.vcf | grep 65745
1 65745 . A G 61 PASS ANN=G|upstream_gene_variant|MODIFIER|OR4F5|ENSG00000186092|transcript|ENST00000335137|protein_coding||c.-3346A>G|||||3346|,G|downstream_gene_variant|MODIFIER|OR4G11P|ENSG00000240361|transcript|ENST00000492842|unprocessed_pseudogene||n.*1858A>G|||||1858|,G|intergenic_region|MODIFIER|OR4G11P-OR4F5|ENSG00000240361-ENSG00000186092|intergenic_region|ENSG00000240361-ENSG00000186092|||n.65745A>G||||||;CALLERS=vardict,varscan;LSEQ=GTTAACTTAAATACTTAGAG;MSI=3;MSILEN=1;RSEQ=AATTAATATGAATAATGTTA;SAMPLE=DO51159-Tumor;SHIFT3=3;SOMATIC;SOR=0;SSF=0.51648;STATUS=StrongSomatic;TYPE=SNV GT:AD:ADJAF:AF:ALD:BIAS:DP:HIAF:MQ:NM:ODDRATIO:PMEAN:PSTD:QSTD:QUAL:RD:SBF:SN:VD 0/0:4,0:0:0:0,0:0,0:4:1:27:0:0:28.8:1:1:39.3:4,0:1:8:0 0/1:8,3:0:0.2727:3,0:0,0:11:0.2727:25:1:0:33.3:1:1:38.7:8,0:1:6:3
Lastly, as you may see, I specified only two samples for the run. Is there a mistake about file targeting?
details:
- algorithm:
aligner: false
ensemble:
numpass: 2
indelcaller: scalpel
platform: illumina
quality_format: illumina
realign: false
recalibrate: false
remove_lcr: true
variantcaller:
- mutect
- vardict
- varscan
- freebayes
analysis: variant2
description: DO51159-Normal
files:
- s3://tuncproject/icgcrun/input/normal.bam
genome_build: GRCh37
metadata:
batch: ICGC
phenotype: normal
- algorithm:
aligner: false
ensemble:
numpass: 2
indelcaller: scalpel
platform: illumina
quality_format: illumina
realign: false
recalibrate: false
remove_lcr: true
variantcaller:
- mutect
- vardict
- varscan
- freebayes
analysis: variant2
description: DO51159-Tumor
files:
- s3://tuncproject/icgcrun/input/tumor.bam
genome_build: GRCh37
metadata:
batch: ICGC
phenotype: tumor
fc_date: '2015-04-14'
fc_name: ICGC-trials
resources:
gatk:
jar: s3://tuncproject/gatktools/GenomeAnalysisTK.jar
mutect:
jar: s3://tuncproject/gatktools/mutect-1.1.7.jar
upload:
bucket: tuncproject
dir: ../final
folder: icgcrun/input/final
method: s3
region: us-east-1
Finally, Gemini seems very informative and benefits the final variants calls. Therefore, I am pleased to keep that information.
Thank you very much for your help,
Best,
Tunc.
Tunc; Thanks for the help debugging this. This line looks correct to me, so it might be that a previous line is signaling there should be 4 samples, while this line has the correct 2 samples. If you look at the same file. what does the sample header look like:
zgrep ^#CHROM /mnt/work/gemini/ICGC-ensemble.vcf.gz
Based on the error message, my guess is one of the calling methods has 4 samples in the #CHROM line and this is causing the confusion. I'm specifically worried that you have aligner: false
and don't have bam_clean: picard
set. The bam_clean
step (or running an alignment) handles correctly setting the read group information in the BAM file to match the sample names you specified (DO51159-Tumor
and DO51159-Normal
). Did you manually correct the BAM files prior to feeding to bcbio? If not we might have ended up with two sample names: the original with whatever was in the BAM file read group, and the bcbio specified one (when it corrects callers that don't use read group information and output generic names like TUMOR/NORMAL).
This might also help identify if something looks wrong in one of the outputs:
ls */*-effects.vcf.gz | xargs zgrep ^#CHROM
All of the sample lines should have two sample names (DO51159-Tumor
and DO51159-Normal
).
Hope this helps.
This is the output of that specific command you suggested.
#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT 140e5014-bdd6-4663-9404-234c7f9e927d DO51159-Normal DO51159-Tumor a9ec7d9e-b179-4782-a589-43c7d1642be9
I checked what are those entries. The one that starts with "a9ec.." it is one of the broad output names. But I dont know why it is in the file. I couldnt find any entries to the first one.
Like this;
a9ec7d9e-b179-4782-a589-43c7d1642be9.broad-snowman.20151107.germline.indel.vcf.gz
I think you are TOTALLY right about your guess. It is the group names. My entries related to TUMOR/NORMAL in the configuration file caused this problem.
O mai god @chapmanb, you were totally right about the problem. THANK YOU THANK YOU!!!
ubuntu@frontend001:/encrypted/project10/work$ ls */*-effects.vcf.gz | xargs zgrep ^#CHROM
freebayes/ICGC-effects.vcf.gz:#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT a9ec7d9e-b179-4782-a589-43c7d1642be9 140e5014-bdd6-4663-9404-234c7f9e927d
gemini/ICGC-freebayes-decompose-effects.vcf.gz:#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT a9ec7d9e-b179-4782-a589-43c7d1642be9 140e5014-bdd6-4663-9404-234c7f9e927d
gemini/ICGC-vardict-decompose-effects.vcf.gz:#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT DO51159-Tumor DO51159-Normal
mutect/ICGC-effects.vcf.gz:#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT 140e5014-bdd6-4663-9404-234c7f9e927d DO51159-Normal DO51159-Tumor a9ec7d9e-b179-4782-a589-43c7d1642be9
vardict/ICGC-effects.vcf.gz:#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT DO51159-Tumor DO51159-Normal
varscan/ICGC-effects.vcf.gz:#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT DO51159-Normal DO51159-Tumor
So, should remove that DO51159-Normal/Tumor
from my configuration file ? or could you please guide me on which editing should I do next to fix this problem? Should there be a option where it uses the default which basically takes from the header of that bam?
One last question,
In order to finalise this run successfully, can I bcbio_vm.py run -n ...
and continue where was I left off with the updated configuration file ? or it starts calling all the mutations again? When I have alinged files I know that bcbio continue from that point but is it same for the variant calling ?
Thank you very much for identifying the problem.
Best regards,
Tunc.
Tunc; Thanks for confirming this is the issue and sorry about the problem. I will add some code in bcbio to check for this case and warn you before you get to this late stage and have mismatched sample names.
Fixing will unfortunately require some re-running. You have two choices. The first is to use the ICGC names (140e5014-bdd6-4663-9404-234c7f9e927d and a9ec7d9e-b179-4782-a589-43c7d1642be9). You can edit your sample YAML file to replace these with your custom names (D051159) and you'll have to figure out which is tumor and which is normal by looking at the input BAM fijles (samtools view -H tumor.bam | grep RG
). After doing that you'd need to do:
rm -rf prealign checkpoints_parallel gemini ensemble
rm -rf mutect vardict varscan
The second option is to have bcbio fix the header by adding bam_clean: picard
or do the alignment by adding aligner: bwa
. Then you'd need to do:
rm -rf prealign checkpoints_parallel gemini ensemble
rm -rf mutect freebayes
And in both cases re-run from there. Sorry about the problem and hope this helps get your analysis finished.
Tunc; I looked into the code and am not sure how your run circumvents our checks for mismatched sample names. We have a check for your problem and should have caught it up front, but did not somehow. Could you report the output of:
samtools view -H inputs/tuncproject/icgcrun/input/tumor.bam | grep ^@RG
samtools view -H inputs/tuncproject/icgcrun/input/normal.bam | grep ^@RG
and I'll try to dig more to see what we're missing that prevents detecting this error at the start of a run. Thanks again for the help debugging.
Brad;
Here is the information that you asked. I figured out which SM tag is belong to which sample. I think the problem caused by the decription part. Apparently, all the other callers but freebayes took description in put as sample name and tried to process it as a different sample. ( I learned this because sometimes different libraries can be used for sequencing thus they are labeled by different SM tags to distinguish during alignment/ mutation calling. ) You should be look at SM
in @RG
If I did not specify description input, what would happen? Would callers use the original SM tag information in the bam files??
Could you inform me regarding this information after you get done with your task ? Because I dont want to manually check @RG line of all of my bams manually for 214 samples?
I am really happy to contribute bcbio :)
[ec2-user@ip-172-31-57-166 input]$ samtools view -H tumor.bam | grep SM | grep SM
@RG ID:OICR:CPCG_0414_Pr_P_PE_607_WG.1 PL:ILLUMINA CN:OICR PI:607 DT:2014-03-27T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Pr_P_PE_607_WG SM:a9ec7d9e-b179-4782-a589-43c7d1642be9 PU:OICR:140327_SN801_0162_BC3RMVACXX_8 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Pr_P_PE_607_WG.2 PL:ILLUMINA CN:OICR PI:607 DT:2014-04-11T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Pr_P_PE_607_WG SM:a9ec7d9e-b179-4782-a589-43c7d1642be9 PU:OICR:140411_SN203_0228_BC3R9VACXX_8 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Pr_P_PE_620_WG.1 PL:ILLUMINA CN:OICR PI:620 DT:2014-04-03T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Pr_P_PE_620_WG SM:a9ec7d9e-b179-4782-a589-43c7d1642be9 PU:OICR:140403_h803_0182_AC4CT6ACXX_1 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Pr_P_PE_620_WG.2 PL:ILLUMINA CN:OICR PI:620 DT:2014-04-29T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Pr_P_PE_620_WG SM:a9ec7d9e-b179-4782-a589-43c7d1642be9 PU:OICR:140429_SN804_0189_AC4DR3ACXX_1 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Pr_P_PE_630_WG.1 PL:ILLUMINA CN:OICR PI:630 DT:2014-04-03T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Pr_P_PE_630_WG SM:a9ec7d9e-b179-4782-a589-43c7d1642be9 PU:OICR:140403_h803_0182_AC4CT6ACXX_2 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Pr_P_PE_630_WG.2 PL:ILLUMINA CN:OICR PI:630 DT:2014-04-29T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Pr_P_PE_630_WG SM:a9ec7d9e-b179-4782-a589-43c7d1642be9 PU:OICR:140429_SN804_0189_AC4DR3ACXX_2 PG:fastqtobam
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Pr_P_PE_607_WG.1\tCN:OICR\tDT:2014-03-27T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Pr_P_PE_607_WG\tPG:fastqtobam\tPI:607\tPL:ILLUMINA\tPU:OICR:140327_SN801_0162_BC3RMVACXX_8\tSM:a9ec7d9e-b179-4782-a589-43c7d1642be9 /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_0 PN:bwa VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Pr_P_PE_630_WG.2\tCN:OICR\tDT:2014-04-29T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Pr_P_PE_630_WG\tPG:fastqtobam\tPI:630\tPL:ILLUMINA\tPU:OICR:140429_SN804_0189_AC4DR3ACXX_2\tSM:a9ec7d9e-b179-4782-a589-43c7d1642be9 /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_1 PN:bwa PP:bamsort_0 VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Pr_P_PE_620_WG.2\tCN:OICR\tDT:2014-04-29T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Pr_P_PE_620_WG\tPG:fastqtobam\tPI:620\tPL:ILLUMINA\tPU:OICR:140429_SN804_0189_AC4DR3ACXX_1\tSM:a9ec7d9e-b179-4782-a589-43c7d1642be9 /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_2 PN:bwa PP:bamsort_1 VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Pr_P_PE_620_WG.1\tCN:OICR\tDT:2014-04-03T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Pr_P_PE_620_WG\tPG:fastqtobam\tPI:620\tPL:ILLUMINA\tPU:OICR:140403_h803_0182_AC4CT6ACXX_1\tSM:a9ec7d9e-b179-4782-a589-43c7d1642be9 /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_3 PN:bwa PP:bamsort_2 VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Pr_P_PE_607_WG.2\tCN:OICR\tDT:2014-04-11T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Pr_P_PE_607_WG\tPG:fastqtobam\tPI:607\tPL:ILLUMINA\tPU:OICR:140411_SN203_0228_BC3R9VACXX_8\tSM:a9ec7d9e-b179-4782-a589-43c7d1642be9 /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_4 PN:bwa PP:bamsort_3 VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Pr_P_PE_630_WG.1\tCN:OICR\tDT:2014-04-03T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Pr_P_PE_630_WG\tPG:fastqtobam\tPI:630\tPL:ILLUMINA\tPU:OICR:140403_h803_0182_AC4CT6ACXX_2\tSM:a9ec7d9e-b179-4782-a589-43c7d1642be9 /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_5 PN:bwa PP:bamsort_4 VN:0.7.8-r455
ec2-user@ip-172-31-57-166 input]$ samtools view -H normal.bam | grep SM
@RG ID:OICR:CPCG_0414_Ly_R_PE_000_WG.1 PL:ILLUMINA CN:OICR PI:000 DT:2014-03-05T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Ly_R_PE_000_WG SM:140e5014-bdd6-4663-9404-234c7f9e927d PU:OICR:140305_SN1017_0409_BC3VKFACXX_4 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Ly_R_PE_000_WG.2 PL:ILLUMINA CN:OICR PI:000 DT:2014-03-05T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Ly_R_PE_000_WG SM:140e5014-bdd6-4663-9404-234c7f9e927d PU:OICR:140305_SN1017_0409_BC3VKFACXX_5 PG:fastqtobam
@RG ID:OICR:CPCG_0414_Ly_R_PE_000_WG.3 PL:ILLUMINA CN:OICR PI:000 DT:2014-03-05T00:00:00+06:00 LB:WGS:OICR:CPCG_0414_Ly_R_PE_000_WG SM:140e5014-bdd6-4663-9404-234c7f9e927d PU:OICR:140305_SN1017_0409_BC3VKFACXX_6 PG:fastqtobam
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Ly_R_PE_000_WG.1\tCN:OICR\tDT:2014-03-05T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Ly_R_PE_000_WG\tPG:fastqtobam\tPI:000\tPL:ILLUMINA\tPU:OICR:140305_SN1017_0409_BC3VKFACXX_4\tSM:140e5014-bdd6-4663-9404-234c7f9e927d /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_0 PN:bwa VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Ly_R_PE_000_WG.2\tCN:OICR\tDT:2014-03-05T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Ly_R_PE_000_WG\tPG:fastqtobam\tPI:000\tPL:ILLUMINA\tPU:OICR:140305_SN1017_0409_BC3VKFACXX_5\tSM:140e5014-bdd6-4663-9404-234c7f9e927d /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_1 PN:bwa PP:bamsort_0 VN:0.7.8-r455
@PG CL:/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/bin/PCAP-core-1.1.1/bin/bwa mem -t 15 -p -T 0 -R @RG\tID:OICR:CPCG_0414_Ly_R_PE_000_WG.3\tCN:OICR\tDT:2014-03-05T00:00:00+06:00\tLB:WGS:OICR:CPCG_0414_Ly_R_PE_000_WG\tPG:fastqtobam\tPI:000\tPL:ILLUMINA\tPU:OICR:140305_SN1017_0409_BC3VKFACXX_6\tSM:140e5014-bdd6-4663-9404-234c7f9e927d /mnt/home/seqware/provisioned-bundles/Workflow_Bundle_BWA_2.6.1_SeqWare_1.1.0-alpha.5/Workflow_Bundle_BWA/2.6.1/data/reference/bwa-0.6.2/genome.fa.gz - ID:bwa_2 PN:bwa PP:bamsort_1 VN:0.7.8-r455
Tunc; Thanks for the read group details, this helped a lot in tracking down the underlying problem. In our check we only issue a warning if there are multiple read groups (which you have) but as a result didn't raise an error because the read group samples (SM) don't match the description. I fixed this so it'll error out on the mismatch up front instead of after and we're building a new Docker container soon that should be available in an hour or so and will check this going forward. Thanks for the help debugging the problem and hope the re-run and subsequent runs go smoother with this check in place.
Dear Brad;
I tried running final template on bam files. Actually I think it did pretty well. However, during the ensemble phase I got an error and pipe got broken. I believe this problem might be related with the additional output which are i think a some other way of describing chromosomes. I believe ensemble algorithm fails at that step. I have those
GL00..
files in all of my callers outputs'. Have you ever come across with this kind of issue?bcbio -n 36 s3://tuncproject/icgcproject/input/deneme8/.yaml
( this is the exact command that brought me to his point.) Will is start from the ensemble step ? or will it start from the beginning? This is my final situation.My error related ensemble; bcbio called the following command;
then I got the following error.
If I pass this step, hopefully I won't bother you for a while. I owe you too much !
Best regards,
Tunc.