...
- The class must be public.
- It must have a public constructor that takes no arguments.
- The driver should not do initialization in the constructor but should use the detectorChanged() or startOfData() methods, instead.
- The driver's set methods should always be of the form
Set methods not of this form will not be accessible as XML parameters.No Format public void set[ParameterName]([type] [varName])
- The use of sub-drivers is discouraged due to these being inaccessible to the job manager, though it is still possible to use them.
Running a Specific LCSim Release (New Way)
Running your job with the lcsim jar is straightforward. Download the bin jar from the repository and use the java command to execute your steering file.
| No Format |
|---|
wget http://www.lcsim.org/maven2/org/lcsim/lcsim/1.14-SNAPSHOT/lcsim-1.14-SNAPSHOT-bin.jar
java -jar ./lcsim-1.14-SNAPSHOT-bin.jar mySteeringFile.xml
|
The steering file must be provided by the user, of course.
Running a Specific LCSim Release (Old Way)
| Warning | ||
|---|---|---|
| ||
This section is out of date. Running a jar is now done using the bin jar, not a zip file. Those who need to run older versions of lcsim for some reason may need to follow these instructions if the bin jar is not present in the lcsim maven repository. |
Older builds (1.4 for instance) may use this run procedure.
When an LCSim release is made, a zip file is created containing the LCSim jar and all its dependencies. Running a specific version of LCSim from the command line is as simple as downloading this zip file, unzipping it, and using the java command to run the jar with your XML input.
...