[Halld-offline] Monitoring Launch: 2017-01 ver34

[Alexander Austregesilo]

Dear Colleagues,

As a last check before the next full REST production launch of the 2017 
data, we made a monitoring launch over 2 files of each run (ver34). The 
usual monitoring plots can be found on the web pages linked below. 
Please have a close look at all relevant monitoring plots and report 
problems quickly. We are planning to launch the REST production very soon.

If I compare this monitoring launch with the last one we did on the full 
2017 data (ver29, November 2017), I see an increase of about 50% in both 
cpu and wall time. This effect could be explained by a larger number of 
reconstructed tracks. This itself is reflected in an increase of 
reconstructed rhos per trigger which is also about 50%, and the increase 
in omegas is even larger!

Unfortunately, about 1% of the jobs did not finish within a reasonable 
amount of time. This effect seems to be reproducible and I can provide a 
list of the files.

https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/plotBrowser.py
https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/runBrowser.py
https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/timeSeries.py
https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/versionBrowser.py 


The merged histogram files can be found on the work disk at:
/work/halld/data_monitoring/RunPeriod-2017-01/mon_ver34/rootfiles/

The REST files and several skims can be accessed here:
/cache/halld/offline_monitoring/RunPeriod-2017-01/ver34/REST/

Best regards,

Alex

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-offline/attachments/20180711/cfac4ced/attachment.html>