I believe I have fixed this in FWS v1.8.3 - thank you!
Let me know if you still encounter any issues. Note that if your time permits, you can always submit a PR to FireWorks with a patch / addition with a specific solution if you have it.
Best,
Anubhav
···
On Monday, December 10, 2018 at 3:20:53 AM UTC-8, Akira Takahashi wrote:
Hi,
I executed the following command on terminal
qlaunch -r singleshot -f 2
``
and output was
2018-12-10 19:59:14,815 INFO reserved FW with fw_id: 15
…
``
.
The problem is that fw_id actually submitted (fw_id: 15) differs from that I specified (-f 2).
I think this is because args.fw_id is not specified into any function in fireworks/scripts/qlaunch_run.py. (it should be specified in 69-71th lines?)
I checked the option works well with the latest version.
Thank you for fix!
I will submit a pull request as possible when the problem is easy.
Best,
Akira Takahashi
2018年12月15日土曜日 7時00分57秒 UTC+9 Anubhav Jain:
···
Hi Akira,
I believe I have fixed this in FWS v1.8.3 - thank you!
Let me know if you still encounter any issues. Note that if your time permits, you can always submit a PR to FireWorks with a patch / addition with a specific solution if you have it.
Best,
Anubhav
On Monday, December 10, 2018 at 3:20:53 AM UTC-8, Akira Takahashi wrote:
Hi,
I executed the following command on terminal
qlaunch -r singleshot -f 2
``
and output was
2018-12-10 19:59:14,815 INFO reserved FW with fw_id: 15
…
``
.
The problem is that fw_id actually submitted (fw_id: 15) differs from that I specified (-f 2).
I think this is because args.fw_id is not specified into any function in fireworks/scripts/qlaunch_run.py. (it should be specified in 69-71th lines?)