...
| No Format |
|---|
<lcsim>
<inputFiles>
<fileUrl />
<file />
</inputFiles>
<control>
<dryRun />
<logFile />
<cacheDirectory />
<skipEvents />
<numberOfEvents />
<verbose />
<printDriverStatistics />
<printSystemProperties />
<printUserClassPath />
<printDriversDetailed />
</control>
<classpath>
<jarUrl />
<jar />
</classpath>
<execute>
<driver name="ExampleDriver" />
</execute>
<drivers>
<driver name="ExampleDriver" type="org.lcsim.example.ExampleDriver">
<exampleParam />
</driver>
</drivers>
</lcsim>
|
...
Some batch systems may not support remote file access via URL. Check with your administrator.
Job Control
The <control> section contains parameters that control the batch job, including the number of events to run and whether various debugging output should be printed.
Setting <dryRun> to true means that the job manager will create the drivers but will not run the job. This can be used to check that your driver setup and arguments are correct.
The <logFile> element is used to specify a log file location. If no log file is specified, the job output goes to the terminal screen.
The <cacheDirectory> specifies the root directory to be used for caching remote data files.
The <numberOfEvents> is the total number of events that will be run. All events will be processed if this argument is left blank.
The <skipEvents> argument tells the job manager to skip a number of events up-front before processing the rest.
The <verbose> tag should be set to true for verbose debugging output.
These tags can also be set to true to print out additional information about the job: <printDriverStatistics>, <printSystemProperties>, <printUserClassPath>, and <printDriversDetailed>.
Running a Specific LCSim Release
...