Search/Navigation:
Related:
SLAC/EPP/HPS Public
Jefferson Lab/Hall B/HPS Run Wiki
S30XL-LESA/LDMX
...
Some of these arguments are similar to the job manager, but the steering file is supplied in a different way. Evio2Lcio uses a command switch to specifiy the steering whereas the job manager expects this as an extra argument without a command switch.
Run scripts that wrap a number of HPS Java command line utilities are generated when building the distribution.
After the build completes, they should be found in this HPS Java directory.
No Format |
---|
distribution/target/appassembler/bin/ |
For instance, the EvioToLcio utility can be run using this script.
Code Block | ||
---|---|---|
| ||
distribution/target/appassembler/bin/evio2lcio.sh [...] |
These scripts have several advantages over running the java commands yourself.
Using symlinks to these scripts works fine e.g.
Code Block | ||
---|---|---|
| ||
ln -s distribution/target/appassembler/bin/evio2lcio.sh
./evio2lcio.sh |
When using these scripts, you cannot directly supply Java system properties, so the JAVA_OPTS variable should be used instead.
Code Block | ||
---|---|---|
| ||
export JAVA_OPTS="-DdisableSvtAlignmentConstants=true" |
The full list of Java system properties to be used should be included in this variable.
You should not set -Xmx or -Djava.util.logging.config.class as they are already set by the run scripts.
...
Code Block | ||
---|---|---|
| ||
cd hps-java-trunk; java -Djava.util.logging.config.file=logging/src/main/resources/org/hps/logging/config/logging.properties |
Each logger is configured for an entire package rather than individual classes.
No Format |
---|
# evio
org.hps.evio.level = CONFIG |
...
/logging/config/logging.properties [...] |
You can also activate a Java class which will load this configuration.
Code Block | ||
---|---|---|
| ||
java -Djava.util.logging.config.class=org.hps.logging.config.DefaultLoggingConfig [...] |
These are the available log levels, in descending order.
...
This is defined in the config file as follows.
No Format |
---|
# default global level global level .level = WARNING |
So if a package is not explicitly configured, it will inherit the WARNING log level from the global logger.
In the config file, loggers are defined and configured by package rather than class.
No Format |
---|
# evio org.hps.evio.level = WARNING |
So if a package is not explicitly configured, it will inherit the WARNING log level from the global logger.
CONFIG |
In the above config, any logger in the org.hps.evio package will have a log level of CONFIG.
A class's logger is typically be defined using the following templateA logger should typically be defined as follows in an HPS Java class.
Code Block | ||
---|---|---|
| ||
package org.example; import java.util.logging.Logger; class MyClass { static private final Logger LOGGER = Logger.getLogger(MyClass.class.getPackage().getName()); void someMethod() { LOGGER.info("some method was called"); } } |
...