You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using this as part of https://github.com/epi2me-labs/wf-transcriptomes/
I am able to run make batches, generating 0-48 batches, and the following clustering step failed.
The error message is slurmstepd: error: Detected 3526 oom_kill events in StepId=12206690.batch. Some of the step tasks have been OOM Killed.
But when I examine the log files, all job_level_0 output was generated, but most level_1 output not.
I tried to run the failed script from level_1.sh
Loaded input batch from clusters/isONcluster_8.cer:
Batch number: 8
Batch range: [219434,255621]
Depth: 0
Nr sequences: 36188
Nr bases: 50286190
Nr clusters: 38
Nr nontrivial clusters: 38
Minimizers in database: 23082
Loaded input batch from clusters/isONcluster_9.cer:
Batch number: 9
Batch range: [255622,293538]
Depth: 0
Nr sequences: 37917
Nr bases: 50287047
Nr clusters: 33
Nr nontrivial clusters: 32
Minimizers in database: 0
Generating consensus using spoa algorithm: semi-global
Clustering mode: sahlin
Filtered out 0 input clusters smaller than 2.
Finished clustering!
Alignment invocation count: 0 (0%)
Consensus invocation count: 33 (100%)
Number of clusters larger than 1: 38
Output batch statistics:
Batch number: 8
Batch range: [219434,293538]
Depth: 1
Nr sequences: 74105
Nr bases: 100573237
Nr clusters: 38
Nr nontrivial clusters: 38
Minimizers in database: 24370
Output batch written to: clusters/isONcluster_53.cer
I noticed the minimizes is 0 for the right cluster, but not sure if this is related. This error caused then all subsequent issues. The file sizes seem small, and I have requested 16GB per core in a slurm management system.
I need some help to run this if you could kindly have a look at the issue.
Thanks a lot.
The text was updated successfully, but these errors were encountered:
alexyfyf
changed the title
minimizer counts is not read after self clustering
some level_1 output is not generated
Jun 6, 2023
Looks like your job was killed because of Out Of Memory (OOM) reading from slurmstepd: error: Detected 3526 oom_kill events in StepId=12206690.batch. Some of the step tasks have been OOM Killed.
So giving more memory may help. I am not the developer of this tool so I canot give detailed advice or insights on its implementation, but I developed isONclust which should give identical results to isONclust2. So I can help you with isONclust if you also decide to try that tool.
Note though that isONclust2 was developed to improve mainly speed over isONclust, as original isONclust is implemented in Python. How many reads do you have?
Hi Kristoffer, thank you for your suggestion, I'll try isONclust and see if it runs.
The OOM issue looks weird, as these level 1 files are typically a few MB (definitely <100MB). Not sure why those specific ones failed.
Hi team,
I am using this as part of https://github.com/epi2me-labs/wf-transcriptomes/
I am able to run make batches, generating 0-48 batches, and the following clustering step failed.
The error message is
slurmstepd: error: Detected 3526 oom_kill events in StepId=12206690.batch. Some of the step tasks have been OOM Killed.
But when I examine the log files, all job_level_0 output was generated, but most level_1 output not.
I tried to run the failed script from level_1.sh
It showed segmentation fault (core dumped).
There are some were successfully run for level_1
I noticed the minimizes is 0 for the right cluster, but not sure if this is related. This error caused then all subsequent issues. The file sizes seem small, and I have requested 16GB per core in a slurm management system.
I need some help to run this if you could kindly have a look at the issue.
Thanks a lot.
The text was updated successfully, but these errors were encountered: