FIX: strict syntax for alliance_canada

[maxulysse]

---

name: New Config
about: A new cluster config

Please follow these steps before submitting your PR:

• If your PR is a work in progress, include [WIP] in its title
• Your PR targets the master branch
• You've included links to relevant issues, if any

Steps for adding a new config profile:

• Add your custom config file to the conf/ directory
• Add your documentation file to the docs/ directory
• Add your custom profile to the nfcore_custom.config file in the top-level directory
• Add your profile name to the profile: scope in .github/workflows/main.yml
• OPTIONAL: Add your custom profile path and GitHub user name to .github/CODEOWNERS (**/<custom-profile>** @<github-username>)

[maxulysse]

@jerryakii @MareikeJaniak @CMonnin I tried to update this config to work with the coming new syntax (cf https://nf-co.re/blog/2026/configs-strict-syntax).
Please have a look, and let us know if it's working for you

[MareikeJaniak]

The parameter for the SLURM_ACCOUNT isn't getting passed with the new version of the config file, causing the pipeline to crash when it tries to submit jobs. I can't figure out why, though. As a sanity check, I just tested with the old version and it's working as expected.

[CMonnin]

looks like the $SLURM_ACCOUNT was being overwritten to '' if you weren't on trillium

[MareikeJaniak]

Thanks! It's working now.

[CMonnin]

hello,
ive refactored the config to use $CC_CLUSTER instead of hostname as it's more robust.

[MareikeJaniak]

I'm still getting this warning, but things do seem to run as expected:

WARN: The following invalid input values have been detected:

* --max_cpus: 192
* --max_time: 7d
* --max_memory: 750 GB
* --cluster_name: rorqual

[CMonnin]

I'm still getting this warning, but things do seem to run as expected:

WARN: The following invalid input values have been detected:

* --max_cpus: 192
* --max_time: 7d
* --max_memory: 750 GB
* --cluster_name: rorqual

What did you run?
@MareikeJaniak
I did some basic testing on the clusters, i just ran
nextflow -c conf/alliance_canada.config config and got the expected outputs.

[MareikeJaniak]

@CMonnin I ran the rnaseq pipeline test described here:
https://docs.alliancecan.ca/wiki/Nextflow

Running nextflow -c conf/alliance_canada.config config does also give me the expected outputs.

[CMonnin]

@MareikeJaniak i believe the warnings are from the json schema. I think it's ok to ignore them for now. I'm ok with approving this

[maxulysse]

@CMonnin You changed the startsWith back to ==, won't that cause issues on your side?

[CMonnin]

I changed the check to use the env variable 'CC_CLUSER' which exists in each cluster and is just the name of the cluster. It's easier to match now.

…

On Mon, Apr 20, 2026, 3:34 a.m. Maxime U Garcia ***@***.***> wrote: *maxulysse* left a comment (nf-core/configs#1069) <#1069?email_source=notifications&email_token=A3CIGGCI5KWELGPDITY6RL34WXHIHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXHA3DQNZUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4278687446> @CMonnin <https://github.com/CMonnin> You changed the startsWith back to ==, won't that cause issues on your side? — Reply to this email directly, view it on GitHub <#1069?email_source=notifications&email_token=A3CIGGCI5KWELGPDITY6RL34WXHIHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXHA3DQNZUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4278687446>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3CIGGC2UDSXAQZXLP6326D4WXHIHAVCNFSM6AAAAACXPPGHMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENZYGY4DONBUGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>