...
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:
Code Block ecflow_client --get
This can be done in a python script:
#!/usr/bin/env python2.7 import ecflow try: ci = ecflow.Client() ci.sync_local() # get server definition, by sync with client defs ecflow.PrintStyle.set_style( ecflow.Style.DEFS ) # set printing to show structure print ci.get_defs() # print the returned suite definition except RuntimeError, e: print "Failed: " + str(e)
To retrieve the suite definition and show state:
Code Block ecflow_client --get_state
In python this would be:
#!/usr/bin/env python2.7 import ecflow try: ci = ecflow.Client() ci.sync_local() # retrieve server definition, by sync with client defs ecflow.PrintStyle.set_style( ecflow.Style.STATE ) # set printing to show structure and state print ci.get_defs() # print the returned suite definition except RuntimeError, e: print "Failed: " + str(e)
To list just the node paths and states in python please see: How can I access the path and task states ?
What to do
- Locate the job file and the output file
- Check results by retrieving the suite definition from the server
...