Closed osilander closed 8 months ago
Hi @osilander ,
Thank you very much for opening the issue. As I mentioned in the other one, the 137 error normally is due to not having enough memory. At this moment, each process has default values, if you're running samples that are bigger than we had expected, this could fail. You can override these values by providing a custom nextflow config (using -c
) assigning more memory to the process that is failing. For example:
nextflow_custom.config
process {
withName: makeReport{
memory = 8.GB
}
}
Let me know if this fixes your problem. Thank you very much!
resolved :)
Glad to hear that! Please open a new issue if you detect something else. Thank you very much for using the workflow!
Operating System
CentOS 7
Other Linux
No response
Workflow Version
v1.1.0-g137d59e
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
Workflow Execution - CLI Execution Profile
custom
What happened?
No report generated despite abundance tables being generated. Ran with only BC01 - BC 19 only (as opposed to all 96 barcodes), report generated without issue.
Relevant log output