Right now, when a FW has
{"_pass_job_info":True}
``
as a spec key, the FW name, FW ID and FW launch directory from the parent job passed.
Normally, the FW’s state is redundant, as it should be “COMPLETED” for the child FW to run — unless the FW also has the following as a spec key:
{"_allow_fizzled_parents":True}
``
In this case, the child can run if some or all of the parents are “FIZZLED”
It would be useful in such a case to add the FW’s state when using “_pass_job_info”
This is an easy fix, and I have submitted a pull request for it:
https://github.com/materialsproject/fireworks/pull/335
Hi Martin
Thanks for implementing. At first I was unsure whether this was useful or could lead to problems. But ultimately I think it’s a needed feature. I will merge and release as part of FWS v1.9.4.
···
On Monday, August 5, 2019 at 9:41:58 AM UTC-7, Martin Siron wrote:
Right now, when a FW has
{"_pass_job_info":True}
``
as a spec key, the FW name, FW ID and FW launch directory from the parent job passed.
Normally, the FW’s state is redundant, as it should be “COMPLETED” for the child FW to run — unless the FW also has the following as a spec key:
{"_allow_fizzled_parents":True}
``
In this case, the child can run if some or all of the parents are “FIZZLED”
It would be useful in such a case to add the FW’s state when using “_pass_job_info”
This is an easy fix, and I have submitted a pull request for it:
https://github.com/materialsproject/fireworks/pull/335