It is currently not possible to use the CLI set_priority() command to query workflows, only fireworks. But sometimes the workflow contains metadata that is useful for assigning priorities that is not available in the individual fireworks.
For example, In a 2-FW workflow for DFT structure optimization, the workflow metadata.nelements key indicates the number of distinct elements in the structure. If I want to increase the priority of all single elements, I can't use the command line to do so because the metadata.nelements key is not in the individual FW specs, only the WF.
Per internal discussion with @computron , this could be implemented by adding a command line argument to redirect the query to the WF:
there is a “wf_query” switch in the lpad_run.py code that switches whether the query is done on the FWs or workflows collection
Feature Request:
It is currently not possible to use the CLI
set_priority()command to query workflows, only fireworks. But sometimes the workflow contains metadata that is useful for assigning priorities that is not available in the individual fireworks.For example, In a 2-FW workflow for DFT structure optimization, the workflow
metadata.nelementskey indicates the number of distinct elements in the structure. If I want to increase the priority of all single elements, I can't use the command line to do so because themetadata.nelementskey is not in the individual FW specs, only the WF.Per internal discussion with @computron , this could be implemented by adding a command line argument to redirect the query to the WF: