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
Looking at some of the code on nextflow-core for inspiration & best practices, I noticed that they often use code for memory usage declarations in the config file that looks something like this:
Looking at some of the code on nextflow-core for inspiration & best practices, I noticed that they often use code for memory usage declarations in the config file that looks something like this:
https://github.com/nf-core/rnaseq/blob/3b6df9bd104927298fcdf69e97cca7ff1f80527c/conf/base.config#L15
The idea being that if the first attempt fails for OOM, add memory and try again.
We can also set some error handling to make this specific to OOM errors and limit the number of retries
https://github.com/nf-core/rnaseq/blob/3b6df9bd104927298fcdf69e97cca7ff1f80527c/conf/base.config#L18-L19
We also have the ability to tag individual processes by resource requirements, like this, which seems like it will be a good idea:
https://github.com/nf-core/rnaseq/blob/3b6df9bd104927298fcdf69e97cca7ff1f80527c/conf/base.config#L23-L35
checkmax()
is defined here: https://github.com/nf-core/rnaseq/blob/3b6df9bd104927298fcdf69e97cca7ff1f80527c/nextflow.config#L170-L172The text was updated successfully, but these errors were encountered: