Changes between Version 4 and Version 5 of Public/User_Guide/JUBE
- Timestamp:
- Aug 4, 2016, 2:15:56 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Public/User_Guide/JUBE
v4 v5 47 47 48 48 {{{ 49 deep-chainJobs.sh49 eep-chainJobs.sh 50 50 submit.job.in 51 51 platform.xml … … 54 54 These files won't be modified but the default values can be overwritten in the JUBE xml file. 55 55 56 2) Source files 56 2) Benchmark name and outpath 57 58 {{{ 59 <benchmark name="MAXW-DGTD-compile" outpath="./compile"> 60 }}} 61 62 The outpath describes the benchmark run directory (relative to the position of the input file). This directory will be managed by JUBE and will be automatically created if it doesn’t exist. The directory name and position are very important, because they are the main interface to communicate with your benchmark, after it was submitted. 63 64 3) Source files 57 65 58 66 {{{ … … 65 73 The source files will be copied to the work directory and untar before the compilation. 66 74 67 3) Parameterset75 4) Parameterset 68 76 69 77 {{{ … … 78 86 The values in the set of parameters with name "systemParamter" will be initialized with the default values found in the file "MAXW-DGTD_specs.xml". This last file takes in turn some of the default values of platform.xml and overwrites them. See the file for more information. 79 87 80 4) Step compile88 5) Step compile 81 89 82 90 {{{ … … 91 99 </step> 92 100 }}} 101 102 In the step compile we tell which parameters and source files to use with the tag <use></use>. The <do></do> contains a single shell command. This command will run inside of a sandbox directory environment (inside the outpath directory tree).
