Default mem_mb_per_cpu takes precedence over Snakefile mem_mb

[mwort]

Software Versions

main branch

Describe the bug
If a default mem_mb_per_cpu is set in the profile config.yaml, any resources: mem_mb value provided in the Snakefile is ignored. This is because mem_mb_per_cpu takes precedence in this line. I believe this wasn't by design because any resource given in the Snakefile/rule should override the profile default (hence the bug report).

Possible solutions
Either we distinguish between default and rule resources in the executor before deciding which of the two mem slurm args to add to the sbatch call or we settle on one and merge them when both are given, possibly also solving the bug reported #317, i.e. let sm do the math and only parse mem_mb.

[cmeesters]

Hm, you are right, yet: a non-Snakemake SLURM user would expect to receive an error. Those parameters are mutually exclusive. These two parameters ought to exist for compatibility reasons. Yet, a configuration ought to take precedence over hard coded resources.

For these and similar resources, we could:

1. check for origin
2. check for conflicts (i.e. if both mem parameters are specified at the same level)

How does that sound?

Please understand, that I have little time and currently other priorities - I would welcome any PR, though.