Changes between Version 18 and Version 19 of Public/User_Guide/JUBE

Timestamp:

Aug 27, 2019, 1:26:32 PM (6 years ago)

Author:

Andreas Smolenko

Comment:

—

Public/User_Guide/JUBE

@@ -36 +36 @@
   </include-path>
 }}}
-Under /usr/local/jube2/platform/deep there are a series of files with default values for the DEEP and DEEP-ER systems:
+Under /usr/local/jube2/platform/deep there are a series of files with default values for the DEEP, DEEP-ER and DEEP-EST systems:
 
 {{{
@@ -113 +113 @@
 === Compile application ===
 {{{
-jube2 run MAXW-DGTD-jube-master-SDV.compile.xml
+jube run MAXW-DGTD-jube-master-SDV.compile.xml
 }}}
 A series of output files will be generated and stored under /usr/local/deep-er/sdv-benchmark/applications/MAXW-DGTD/compile/benchmark_id/. The structure is as follows:
@@ -167 +167 @@
 
 {{{
-jube2 run MAXW-DGTD-jube-master-SDV.modules.test.xml --tag woman
+jube run MAXW-DGTD-jube-master-SDV.modules.test.xml --tag woman
 }}}
 will use MAXW-DGTDParameter-woman,
 
 {{{
-jube2 run MAXW-DGTD-jube-master-SDV.modules.test.xml
+jube run MAXW-DGTD-jube-master-SDV.modules.test.xml
 }}}
 will use MAXW-DGTDParameter-head.
@@ -315 +315 @@
 
 {{{
-jube2 analyse benchmarks_modules_test --id jube_id
+jube 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:
@@ -361 +361 @@
 
 {{{
-jube2 result benchmarks_modules_test --id jube_id
+jube 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.