[Halld-offline] Monitoring Launch 2019-01 ver06: PrimeX
Alexander Austregesilo
aaustreg at jlab.org
Thu Feb 27 11:39:27 EST 2020
Dear Colleagues,
We just completed the first monitoring launch over the 2019-01 PrimeX
data set. We processed the first 2 files of each run in the run range
61321 - 61956, selected with the RCDB query "@is_primex_production
and @status_approved". The data was processed with the latest release
"version_4.15.0.xml". The usual monitoring plots can be found on the web
pages:
https://halldweb.jlab.org/data_monitoring/Plot_Browser.html
https://halldweb.jlab.org/cgi-bin/data_monitoring/monitoring/runBrowser.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-2019-01/mon_ver06/rootfiles/
The REST files, random trigger skims and several trees are saved on cache:
/cache/halld/offline_monitoring/RunPeriod-2019-01/ver06/REST/
After several retries, about 5% of the jobs still failed, and the error
logs show 2 prevalentsymptoms:
1) Crash in the CCALShower_factory, e.g.
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver09/log/061752/stderr.061752_001.err
2) Crash in the track extrapolation, e.g.
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver09/log/061508/stderr.061508_000.err
Best regards,
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-offline/attachments/20200227/c18fb39b/attachment.html>
More information about the Halld-offline
mailing list