The new HOOK_WORKFLOW_JOB from ERT removes the need for having a separate workflow file, and should be used for the WF_CREATE_CASE_METDATA.
https://fmu-docs.equinor.com/docs/ert/reference/configuration/keywords.html#hook-workflow-job
We should update the getting started guide.
Current (using a separate workflow file)
LOAD_WORKFLOW ../../bin/workflows/xhook_create_case_metadata
HOOK_WORKFLOW xhook_create_case_metadata PRE_SIMULATION
Change to (and remove reference to workflow file)
HOOK_WORKFLOW_JOB xhook_create_case_metadata WF_CREATE_CASE_METDATA <SUMO_CASEPATH> "--sumo" PRE_SIMULATION
We are currently in the process of updating and removing the arguments from the WF_CREATE_CASE_METDATA job - then it going to look like this
HOOK_WORKFLOW_JOB xhook_create_case_metadata WF_CREATE_CASE_METDATA PRE_SIMULATION
we should also discuss if we want to change the xhook_create_case_metadata name - it is just an internal name used for the workflow, it can be defined whatever.
The new
HOOK_WORKFLOW_JOBfrom ERT removes the need for having a separate workflow file, and should be used for theWF_CREATE_CASE_METDATA.https://fmu-docs.equinor.com/docs/ert/reference/configuration/keywords.html#hook-workflow-job
We should update the getting started guide.
Current (using a separate workflow file)
Change to (and remove reference to workflow file)
We are currently in the process of updating and removing the arguments from the WF_CREATE_CASE_METDATA job - then it going to look like this
we should also discuss if we want to change the
xhook_create_case_metadataname - it is just an internal name used for the workflow, it can be defined whatever.