Search/Navigation:
Related:
SLAC
/EPP/HPS Public
Jefferson Lab/Hall B/HPS Run Wiki
S30XL-LESA/LDMX
Page History
...
| Info | ||
|---|---|---|
| ||
The following examples assume that the '3.0.2-SNAPSHOT' version of the monitoring application is being used but this may change in the future. You should use the jar that is actually created by your local build |
Aside from a dependence on a platform-dependent library used through JNI (covered under the next section), the monitoring application jar is self-contained and can be run as follows.
| No Format |
|---|
java -jar ./target/hps-monitoring-app-3.0.2-SNAPSHOT-bin.jar |
This will start the application with the default options.
There are a few options that can be shown by using the help command line switch.
| No Format |
|---|
java -jar ./target/hps-monitoring-app-3.0.2-SNAPSHOT-bin.jar -h |
To load preexisting settings for the job and connection, a command like this should be executed.
...
| No Format |
|---|
. trunk/et/target/scripts/ldpath.sh |
In the first terminal, start the monitoring app.
| No Format |
|---|
cd trunk/monitoring-app java -jar ./target/hps-monitoring-app-3.0.2-SNAPSHOT-bin.jar |
In the second terminal, start up the ET server.
| No Format |
|---|
cd trunk/et ./target/scripts/et_server_test.sh |
Now, in the monitoring application GUI, you should configure the job parameters in the job panel such as the steering file to be run, if necessary. Then hit the Connect button and make sure that the application connects successfully to the online ET system.
Finally, in the last terminal, a file should be streamed onto the ET ring to activate the event stream in the monitoring application.
| No Format |
|---|
cd trunk/evio ./target/scripts/et_evio_file_producer_test.sh /nfs/slac/g/hps3/data/testrun/runs/evio/hps_001351.evio.0 |
If everything was successful, plots should be created in the monitoring application should start updating with the event data.
Overview
Content Tools