Difference between revisions of "Online Recon - Expert"

From hps run
Jump to navigation Jump to search
Line 8: Line 8:
 
* <tt>softioc_console dqm_server</tt>
 
* <tt>softioc_console dqm_server</tt>
 
* <tt>softioc_console dqm_client</tt>
 
* <tt>softioc_console dqm_client</tt>
 +
 +
A full teardown and restart of all components, including the tomcat server, is in user=hpsrun's $PATH:
 +
 +
<tt> hps-dqm-restart.sh</tt>
  
 
==== TODO ====
 
==== TODO ====
  
 
* 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.
 
* 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.  Meanwhile, a script to do a full teardown and restart is available.
+
* 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.

Revision as of 15:14, 3 August 2021

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.

Everything operates as user=hpsrun, and the startup for all server-side stuff (except tomcat) is configured in $EPICS/apps/iocBoot/procServ.conf. There are 4 components, each of which can be connected to in telnet sessions:

  • softioc_console dqm_et
  • softioc_console dqm_evio2et
  • softioc_console dqm_server
  • softioc_console dqm_client

A full teardown and restart of all components, including the tomcat server, is in user=hpsrun's $PATH:

hps-dqm-restart.sh

TODO

  • 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.