Difference between revisions of "Online Recon - Expert"
| Line 37: | Line 37: | ||
== Clients == | == Clients == | ||
Both should work from any clon machine: | Both should work from any clon machine: | ||
| − | |||
| − | |||
* web browser @ <tt>http://clonfarm2.jlab.org:8080/HPSRecon/</tt> | * web browser @ <tt>http://clonfarm2.jlab.org:8080/HPSRecon/</tt> | ||
| − | ** this does not update automatically (currently) | + | ** this does not update automatically (currently) but requires a manual refresh |
** but clicking on a detector displays many plots simultaneously | ** but clicking on a detector displays many plots simultaneously | ||
| + | * jas3-->Tools-->Connect [[Image:jas3-onlinerecon.png|200px]] | ||
| + | ** this has the advantage that it refreshes automatically | ||
== Notes == | == Notes == | ||
Revision as of 15:09, 3 August 2021
Servers
Currently everything in this section is running on clonfarm2, but that may change.
Software Installations
The core HPS java software builds for online, multi-threaded reconstruction live in ~hpsrun/online_recon and were installed using the instructions on confluence.
We may decide the hps-java installation there should be a symlink to a standard one elsewhere, but note it requires an extra installation step and (currently) a non-master git branch.
If the tomcat servlet needs updating, it will need to be rebuilt and redpolyed.
Operations
Everything operates as user=hpsrun and startup originates in $EPICS/apps/iocBoot/procServ.conf. There are 4 components, started sequentially, named:
- dqm_et
- just an ET ring, offline only
- dqm_evio2et
- pipes an EVIO file to the ET ring, offline only
- dqm_server
- receives instructions from the client below
- dqm_client
- instructs the server on parameters, e.g. #threads, steering file
Each component is spawned automatically in procServ and is accessible via a telnet session by running
- softioc_console NAME
Once connected, individual components can be interactivly killed, paused, restarted, using the ctrl-X/T sequences (which is printed when you connect). The dqm_client process can also be used interactively within telnet. To disconnect from any telnet session, ctrl-] and then type quit.
Configuration files for all are currently in their startup directory $EPICS/apps/iocBoot/dqm.
A full teardown and restart of all components, including the tomcat server, is in user=hpsrun's $PATH:
- hps-dqm-restart.sh
Clients
Both should work from any clon machine:
- web browser @ http://clonfarm2.jlab.org:8080/HPSRecon/
- this does not update automatically (currently) but requires a manual refresh
- but clicking on a detector displays many plots simultaneously
- jas3-->Tools-->Connect
- this has the advantage that it refreshes automatically
Notes
To Do
- Can the webapp be modified to automatically reload the plots periodically, without the user manually refreshing the web page? This will be important to give users feedback that things are working (and no one wants to have to reload the page). 1 Hz would be great, every few seconds would be good enough.
- The stop/start functionality in the server appears maybe unreliable, and the tomcat servlet also appears to need to be restarted if the recon server is restarted. These things will need to be done in order to zero the histograms, which will be every run and every time beam is away for a significant amount of time. Meanwhile, a script to do a full teardown and restart is available, but it takes many seconds to ensure things are started with appropriate, intermediate delays.
Setup
To setup on a new clon machine, this may be necessary:
- yum install tomcat tomcat-admin-webapps ksh telnet
- edit /etc/tomcat/tomcat-users.xml and enable the "manager-gui" role and "admin" user
Tomcat is somehow unhappy on clonfarm3, appears to be a permissions issue.