-
Notifications
You must be signed in to change notification settings - Fork 8
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
KeyError: 'mod' in workflow_glue/report_mod.py #35
Comments
Hi @lucy924 would it be possibly for you to share the content of the files in:
Thanks in advance |
Sure |
Thank you @lucy924 and apologies for the late reply. I'll have a look and try to reproduce the issue you are finding. Andrea |
@lucy924 I'm still investigating this issue. In the meanwhile, can you try using the latest version of the workflow (v1.4.0)? We released some fixes of modkit, and might be useful to know if you still come across the problem with the latest release. |
The problem seems to be gone now!
But I'm glad it actually finished running! |
BTW, how can we resume the stopped job as before? It seems I can't resume in new EPI2ME GUI once the job is stopped with error. Or can we resume the job via command line? Where can I find the exact nextflow command executed by the GUI here? Thanks. |
@sh0rt2l0ng I did not find out the root cause of this problem, it just stopped happening with that particular run. I don't know if it will pop up in the future though, and will investigate more if I come across it, it's just not a priority for me right now. Would love to know the answer too! |
Operating System
Ubuntu 22.04
Other Linux
No response
Workflow Version
v1.3.1
Workflow Execution
Command line (Cluster)
Other workflow execution
No response
EPI2ME Version
No response
CLI command run
nextflow run epi2me-labs/wf-somatic-variation -params-file params_weka.json -c custom.config -profile singularity -resume
params_weka.json
Workflow Execution - CLI Execution Profile
singularity
What happened?
I'm slowly ironing out all the issues in this test run with one pair of samples on chr1, and the latest issue appears to be in the below section of code according to the error:
wf-somatic-variation/bin/workflow_glue/report_mod.py
Line 205 in ba53c64
I ran it successfully on the demo data but the demo data run didn't do most of the tumour processing which appears to be the problem here.
Thanks!
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response
The text was updated successfully, but these errors were encountered: