Let us now see how our suite ran, type the following:
> ecflow_client --get_state
This command will retrieve the suite definition from the server,
which is is then shown with all the state for each node
If this is not the case, and you might see aborted.
Please check the location (directory) of your ecf script before referring
to your instructor.
The job file created by the server is located in the same directory as the
ecf script, and is named t1.job1.
Compare the files t1.ecf, head.h, tail.h and t1.job1.
The output of the job is located in the same directory as the ecf script,
and is named t1.1.
Retrieving the suite definition¶
To retrieve the suite definition in a form that is parse-able, type:
> ecflow_client --get
This can be done in a python script:
ci = ecflow.Client(); try: ci.sync_local() # get server definition, by sync with client defs ecflow.PrintStyle.set_style( ecflow.Style.DEFS ) # set printing to format that is re-parseable print ci.get_defs() # print the returned suite definition except RuntimeError, e: print "failed: " + str(e);
To retrieve the suite definition and show state:
> ecflow_client --get_state
In python this would be:
ci = ecflow.Client(); try: ci.sync_local # retrieve server definition ecflow.PrintStyle.set_style( ecflow.Style.STATE ) # show node state, this is not re-parseable print ci.get_defs() # print the returned suite definition except RuntimeError, e: print "failed: " + str(e);
What to do:
- Locate the ECF job and the output
- Check results by retrieving the suite definition from the server