Is it possible to use multiple qadapter.yaml

Dear developers,

In some cases, I want to run heavier calculations at faster nodes, while the others at normal nodes.

For this purpose, can I use multiple qadapter.yaml files for qlaunch command?
Or, do you have any other ideas to realize this ?

Best wishes,
Yu

Hi Yu

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”:

https://materialsproject.github.io/fireworks/controlworker.html

Dear Anubhav,

thanks for your prompt reply.
This link indeed describes what I wanted to know.
Sorry I missed it.

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

Please see the documentation

https://materialsproject.github.io/fireworks/queue_tutorial_pt2.html
section: Overriding Queue Parameters within the Firework

you can also have multiple qadapter.yaml files with the -q options as you previously indicated

1 Like