Horizontal Navigation Bar | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Let us now see how our suite ran, type the following:
Code Block | ||
---|---|---|
| ||
ecflow_client --get_state |
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.
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:
Code Block language py import ecflow try: ci = ecflow.Client() # create the client, will read ECF_HOST and ECF_PORT from environment ci.sync_local() # get server definition, by syncing 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 as e: print("Failed:",e)
To retrieve the suite definition and show state:
Code Block language bash ecflow_client --get_state # show state, generated variables, expanded trigger expression, auto added externs ecflow_client --migrate # shows state as comments, used as check point format
In python this would be:
Code Block language py 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, expanded trigger expression, generated variables print(ci.get_defs()) # print the returned suite definition ecflow.PrintStyle.set_style( ecflow.Style.MIGRATE ) # set printing to show structure and state, and node history print(ci.get_defs()) # print the returned suite definition except RuntimeError as e: print("Failed:", 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
Horizontal Navigation Bar | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
HTML | ||||||||||||||||||||||||||
<div id="checking-the-results">
<span id="index-0"></span><span id="id1"></span>
<p>Let us now see how our suite ran:</p>
<div ><pre>> ecf_client --group="get ; show state"</pre>
</div>
<p>This shows the <a href="/wiki/display/ECFLOW/Glossary#term-node"><em >node</em></a> tree and the state of each <a href="/wiki/display/ECFLOW/Glossary#term-node"><em >node</em></a>.
Look at the <a href="/wiki/display/ECFLOW/Glossary#term-task"><em >task</em></a> <strong>t1</strong> if it is <a href="/wiki/display/ECFLOW/Glossary#term-complete"><em >complete</em></a> and the <a href="/wiki/display/ECFLOW/Glossary#term-suite"><em >suite</em></a> is <em>complete</em>
then the run was successful.</p>
<p>If this is not the case, and you might see <a href="/wiki/display/ECFLOW/Glossary#term-aborted"><em >aborted</em></a>.
Please check the location (directory) of your <a href="/wiki/display/ECFLOW/Glossary#term-ecf-script"><em >ecf script</em></a> before referring to your instructor.</p>
<p>The <a href="/wiki/display/ECFLOW/Glossary#term-job-file"><em >job file</em></a> created by the server is located in the same directory as the <a href="/wiki/display/ECFLOW/Glossary#term-ecf-script"><em >ecf script</em></a>, and is named <em>t1.job1</em>.
Compare the files <tt ><span >t1.ecf</span></tt>, <tt ><span >head.h</span></tt>, <tt ><span >tail.h</span></tt> and <tt ><span >t1.job1</span></tt>.</p>
<p>The <strong>output</strong> of the job is located in the same directory as the <a href="/wiki/display/ECFLOW/Glossary#term-ecf-script"><em >ecf script</em></a>, and is named <tt ><span >t1.1</span></tt>.</p>
<p>What to do:</p>
<ol >
<li>Locate the ECF job and the output</li>
</ol>
</div>
|