Closed lucy924 closed 2 weeks ago
@lucy924 we just released v1.3.1 that should address this issue. Could you please try it and let us know if it works?
Andrea
Hi Andrea, Thanks for the update, unfortunately I'm having issues accessing our cluster at the moment and I'll be away next week, just wanted to let you know I'll get to it when I'm back. Thanks, Lucy
Hi Andrea,
I'm trying to run the workflow but I'm running into a memory error, not sure if it's related or not, or if I should open a new issue. Our IT engineer said I may need to increase memory for this particular task either in the workflow config or in the global nextflow config, but I don't know too much about nextflow yet and cautious about messing with your files too much.
The error output is attached, the problem command is:
probs=$( modkit sample-probs B3_CvT_chr1.cram -p 0.1 --interval-size 5000000 --only-mapped --threads 4 2> /dev/null | awk 'NR>1 {ORS=" "; print "--filter-threshold "$1":"$3}' )
The .command.log
output is this:
INFO: Environment variable SINGULARITYENV_TMPDIR is set, but APPTAINERENV_TMPDIR is preferred
INFO: Environment variable SINGULARITYENV_NXF_DEBUG is set, but APPTAINERENV_NXF_DEBUG is preferred
INFO: underlay of /etc/localtime required more than 50 (78) bind mounts
slurmstepd: error: Detected 1 oom_kill event in StepId=811821.batch. Some of the step tasks have been OOM Killed.
Yeah this is similar to what has been notified recently for wf-human-varaition here. You can apply the same solution here, i.e. by passing a custom configuration file.
First, save the following text in a file named e.g. custom.config (it can be any name):
process {
withName: sample_probs {
memory 32.GB
}
}
Then, you can pass it to the workflow with -c custom.config.
I gather that the implausible alignment issue is sorted?
Thanks for the config help, that did indeed sort it. I had to add another process to it too but it's good to know that workaround for when it's out of memory. The workflow has now successfully gone past this original bamstats problem,thank you for fixing it! Lucy
Great closing this issue then.
Andrea
Operating System
Ubuntu 22.04
Other Linux
No response
Workflow Version
v1.3.0
Workflow Execution
Command line (Cluster)
Other workflow execution
No response
EPI2ME Version
No response
CLI command run
Workflow Execution - CLI Execution Profile
singularity
What happened?
The workflow stopped at a bamstats command, telling me that a read "appears to contain implausible alignment information". My understanding was that it performed the alignment as part of the workflow? I have run the wf-alignment on these files previously and didn't have any issues with it. I tried to run this bamstats command outside the workflow but it didn't recognise the
-s
option, and I couldn't specify a different version of bamstats through bioconda. I am running this on a cluster using slurm. Nextflow gave a warning that it doesn't match the required version, but I didn't think that would be why I have this particular error message?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