-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError in wgbs.map Step #66
Comments
This issue in gemBS is almost exactly the same as yours: heathsc/gemBS#37 , although I'm not sure if it is relevant to the version of gemBS used in the pipeline. You may be able to work around by passing in FYI Conda isn't supported by this pipeline. I'd recommend using Docker, or if your HPC doesn't allow it then Singularity would be an option. In theory it should "just work" but in practice there can be quirks due to differences between the runtimes. I haven't tested this pipeline myself with Singularity so I can't say for sure. By the way, looking at your input files, it looks like you might have paired-end data? You have it specified as "wgbs.fastqs": [
[
[
"/resource3/data/WGBS/RawData/222_S2_L004_R1_001.fastq.gz"
],
[
"/resource3/data/WGBS/RawData/222_S2_L004_R2_001.fastq.gz"
]
],
[
[
"/resource3/data/WGBS/RawData/Control_S1_L004_R1_001.fastq.gz"
],
[
"/resource3/data/WGBS/RawData/Control_S1_L004_R2_001.fastq.gz"
]
]
], but if they are in fact paired, the two files should be placed in the same array like this: "wgbs.fastqs": [
[
[
"/resource3/data/WGBS/RawData/222_S2_L004_R1_001.fastq.gz",
"/resource3/data/WGBS/RawData/222_S2_L004_R2_001.fastq.gz"
]
],
[
[
"/resource3/data/WGBS/RawData/Control_S1_L004_R1_001.fastq.gz",
"/resource3/data/WGBS/RawData/Control_S1_L004_R2_001.fastq.gz"
]
]
], |
I went ahead and changed the json input to reflect paired-end data. Thank you! I believe my original json input already had:
Is this what you were referring to? Our HPC doesn't allow Docker. I don't have experience with Singularity, but may need to talk with our sysadmin about adding it (I don't have root privileges). I am re-running with updated json input to see if error is replicated. Will follow up with results. |
Yeah sorry I missed that in the input, that's what I was referring to. In that case it looks OK then. If it still fails I would double check your gemBS version. You can see how it is installed in the pipeline here: Line 37 in f41d0dc
|
Confirming it failed on the same task:
Looks like the gemBS conda installed is gembs-3.2.0 (released june 2018). I think this is likely the problem. From your link earlier, they pushed a new version that incorporated changes fixing this TypeError. Will try updating and get back to you. |
Describe the bug
At the wgbs.map step, I get a TypeError:
How can I resolve this error?
OS/Platform
Caper configuration file
default.conf.txt
Error log
Caper automatically runs a troubleshooter for failed workflows. If it doesn't then get a
WORKFLOW_ID
of your failed workflow withcaper list
or directly use ametadata.json
file on Caper's output directory.cromwell.out.txt
Input JSON File
json_input.txt
The text was updated successfully, but these errors were encountered: