Hello,
I’m trying to figure out if this is a bug, expected behavior or user error on my part… Unfortunately I don’t quite have a minimal example to share.
I’m currently changing my_fworker.yaml frequently as I try out different settings (e.g. changing NPAR/KPAR, vasp_cmd variables), and then after modification I submit a job using qlaunch. However, I often find the old variables are then picked up.
I observed this when changing KPAR: 8 to NPAR: 4. If I submitted the rlaunch command, explicitly providing the path to my config file, it would correctly pick up the new NPAR: 4 setting. However, using qlaunch, which would generate a FW_submit.script containing the exact same rlaunch command, it would incorrectly pick up the old KPAR: 8 setting. I also observed similar behavior when changing the vasp_cmd variable.
I saw the Fireworks website mentions a qlaunch daemon, so I wasn’t sure if my old settings were persisting somewhere I was unaware of? If so, is there a way to make qlaunch detect the new settings? Or is this user error on my part, and I’m not understanding how Fireworks works correctly?
Many thanks for your help!
Best regards,
Matthew