-
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
resource requested too high on Rackham #138
Comments
What's your Nextflow version? |
Also note, that you only need Are you using the project template? |
Nextflow version 23.10.1 Could profile singularity be causing this? |
No, the profile shouldn't cause this. It could be the Nextflow version since I'm not sure when Update the conda environment to use the latest nextflow. Are you using the latest version of the project template? You should then only need to run
|
updated nextflow to 24.10.0, updated
|
There are 1TB nodes, but Meryl should not be requesting that. What's in your |
It seems that
|
Ok, the problem was a Deleting it seems to solve it. |
Yes, that's how you can change settings per project, when running from a remote. https://www.nextflow.io/docs/latest/config.html#configuration-file ( i.e. number 4. takes the I still need to check what the resource limits are in Uppmax, but be aware if that if Martin's change limited it to a standard node, you'll need to increase the |
In the
feature_hic_scaffolding
branch many processes are requesting >20 cpus when using the Uppmax profile. This causes an error and nextflow exits the pipeline.This happened with FASTK_FASTK (requested 36 cpus), I changed it in the config file and then the same happened with HIFIASM (requested 46 cpus). I am using the
uppmax,singularity
profiles.The uppmax.config file has
but it doesn't seem that this is being honoured.
The text was updated successfully, but these errors were encountered: