Skip to content

Conversation

@ens-sb
Copy link
Contributor

@ens-sb ens-sb commented Apr 15, 2024

Dear maintainers,

I have run FastOMA on about 2200 genomes and in order to make the run smoother I have created a customised base config.
The most important change is that I have removed the checking for maximum resource limits from the resource classes. The reson for this that our SLURM cluster has multiple partitions with different resource limits (e.g. bigmem) and the jobs are dynamically allocated to the appropriate queue. I found that with the current base config the jobs are always allocated to the default partition and hence some of them eventually run out of resources, crashing the pipeline.
Also, this config has resource classes with higher memory which can be specified for the processes in the main Nextflow file.
I would like to contribute this alterantive base config to the FastOMA repo in the hope that it will be useful for us and other users.

Best,
Botond

resource limits and larger resource classes.
@sinamajidian sinamajidian changed the base branch from main to dev February 15, 2025 16:26
@sinamajidian sinamajidian merged commit ad519b1 into DessimozLab:dev Feb 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants