You should have two different queue adapters - with the rlaunch command in each queue adapter using a different fireworker file which will lead to pulling different FireWorks (e.g., heavier vs normal jobs) and each queue adapter tuned to the resource you want.
A little more information is in “Controlling the worker of execution”:
Dear developers,
I’d like to raise this topic again: I’ts easy to setup different fireworkers for different fireworks, but they are still use same pbs_qadapter.yaml, and I need different not compatible module loads for them. How I can control which queue adapter yaml file will be used?
Edited: Is this a solution?
I have qlaunch command infinitely running into background. Do I need to have two of them with explicitly set -q QUEUEADAPTER_FILE parameters?
And is there any way to change nnodes, nnodes and pre_rocket in firework specification? That would be much easier to deal with than managing a lot of submission loops