Changes between Version 15 and Version 16 of Public/User_Guide/JUBE

Timestamp:

Aug 5, 2016, 5:44:16 PM (8 years ago)

Author:

Cristina Manzano

Comment:

—

Public/User_Guide/JUBE

@@ -331 +331 @@
 
 and all jobs have in their sandbox a soft link called "shared" pointing to ./benchmarks_modules_test/benchmark_id/execute_shared.
+
+5) Analyse
+
+{{{
+    <analyzer name="analyse" >
+      <use from="MAXW-DGTD_specs.xml">pattern</use>
+      <analyse step="execute">
+        <file>exe/maxdg3DP$k.out</file>
+        <file>job.log</file>
+      </analyse>
+    </analyzer>
+}}}
+
+After the job has run, you can analyse the results with:
+
+{{{
+jube2 analyse benchmarks_modules_test --id jube_id
+}}}
+
+The analyse step will look for the corresponding patterns in the output files, in this case exe/maxdg3DP$k.out and job.log, and the data will be stored inside the benchmark directory. The patterns to look for are specified in the MAXW-DGTD_specs.xml file:
+
+{{{
+  <patternset name="pattern">
+    <pattern name="fluxpvector" unit="W" type="float">\s*Flux of the Poynting vector :\s+$jube_pat_wrd\s*</pattern>
+
+    <pattern name="attau" unit="m" type="float">\s*AT TAU =\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="t" unit="nsec" type="float">\s*T =\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="iterations" unit="" type="int">\s*USING\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="maxcputime" unit="sec" type="float">\s*MAX CPU TIME    :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="realtime" unit="sec" type="float">\s*REAL TIME       :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="timetosolution" unit="sec" type="float">\s*TIME TO SOLUTION:\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="iotime" unit="sec" type="float">\s*I/O TIME        :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="electrtime" unit="sec" type="float">\s*ELECTR TIME     :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="omptime" unit="sec" type="float">\s*OMP TIME        :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="tfluxelectr" unit="sec" type="float">\s*T FLUX ELECTR   :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="tfluxmagnet" unit="sec" type="float">\s*T FLUX MAGNET   :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="tupelectr" unit="sec" type="float">\s*T UP ELECTR     :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="tupmagnet" unit="sec" type="float">\s*T UP MAGNET     :\s+$jube_pat_wrd\s*</pattern>
+    <pattern name="tfourier" unit="sec" type="float">\s*T FOURIER       :\s+$jube_pat_wrd\s*</pattern>
+
+    <pattern name="starttime" type="string" >\(start\)$jube_pat_bl($jube_pat_wrd$jube_pat_bl$jube_pat_wrd)</pattern>
+    <pattern name="stoptime"  type="string" >^\s*\(finished\)\s*(.*)\s*\(</pattern>
+  </patternset>
+}}}
+
+If there are multiple matches inside a single file you can add a reduce option. Normally only the first match will be extracted. See https://apps.fz-juelich.de/jsc/jube/jube2/docu/glossar.html#term-pattern-tag for more information.
+
+6) Result
+
+{{{
+    <result>
+      <use>analyse</use>
+      <table name="result" style="pretty" sort="jube_wp_id">
+        <column>modules</column>
+        <column>iopath</column>
+        <column>iotime</column>
+        <column>starttime</column>
+        <column>stoptime</column>
+      </table>
+    </result>
+
+}}}
+
+The last part is the result table creation. Here you have to use an existing analyser. The <column> contains a pattern or a parameter name. sort is the optional sorting order (separated by ,). The style attribute can be csv or pretty to get different ASCII representations. To create the result table you have to write:
+
+{{{
+jube2 result benchmarks_modules_test --id jube_id
+}}}
+
+The result table will be written to STDOUT and into a result.dat file inside ./benchmarks_modules_test/benchmark_id/result.