Sehyun Oh

1. Community
2. General Discussion
3. input type coercion

Thanks Beri! I missed it out but could fixed it providing a proper path. :) But I still have a same problem with recognizing MuTect outputs as SelectVariants inputs. Here is the error. 2019/06/12 0...

• View comment
• Edited June 12, 2019 01:13
• 0 votes

1. Community
2. General Discussion
3. input type coercion

Thanks Beri! Move SelectVariants call in the scatter bracket fixed the above error. But it seems like SelectVariants can't recognize the output from MuTect1 task. Here is the error. 2019/06/11 20:0...

• View comment
• June 11, 2019 20:25
• 0 votes

1. Community
2. General Discussion
3. Data entity type for MuTect

Hi Sushma, This is THE answer! ;) I don't recall exactly how I uploaded the data tables before, but apparently, they weren't linked properly. I uploaded them making sure the linking steps, and now ...

• View comment
• Edited June 05, 2019 20:22
• 0 votes

1. Community
2. General Discussion
3. Localization of reference files

Hi Sushma, I made this tool worked by putting the index file in the same bucket, and actually that was my initial question: the related reference files (.dict, .idx etc.) need to be stored under th...

• View comment
• June 05, 2019 14:54
• 0 votes

1. Community
2. General Discussion
3. Localization of reference files

I double-checked whether the permission was an issue, but it doesn't seem like. I tested on a tool that worked when I used related files (e.g. index file) stored in a same bucket. I copied the coms...

• View comment
• Edited June 05, 2019 06:37
• 0 votes

1. Community
2. General Discussion
3. Changing machine type for my tool

Thanks for the kind answer on my silly question, Sushma! I totally forgot the runtime attributes in WDL. :p

• View comment
• Edited June 05, 2019 06:26
• 0 votes

1. Community
2. General Discussion
3. Data entity type for MuTect

Sorry about posting a wrong output. This is what I got from mutect2_nio tool. Mutect2.tumor_reads_index - Expected single value for workflow input, but evaluated result set was emptyMutect2.tumor...

• View comment
• June 05, 2019 06:23
• 0 votes

1. Community
2. General Discussion
3. Data entity type for MuTect

Hi Sushma, I tried this.case_sample.WXS_bam_path and this.case_sample.WXS_bai_path for tumor_reads and tumor_read_index attributes, respectively. It failed right away with the error below. M1_only....

• View comment
• June 04, 2019 21:42
• 0 votes

1. Community
2. General Discussion
3. Data entity type for MuTect

I'm not sure whether I can share the workspace - it includes controlled dataset. ;( Actually, re-loading data table didn't cause the above error, but it failed with this error: Failed to evaluate '...

• View comment
• June 03, 2019 21:58
• 0 votes

1. Community
2. General Discussion
3. Data entity type for MuTect

Hi Sushma, I'm using a specific version of MuTect (v.1.7.1), because my tool for the downstream analysis is optimized for this version of MuTect. I tried MuTect2 from the 'Featured Workspace' to un...

• View comment
• June 03, 2019 20:02
• 0 votes