[Primexd] Monitoring Launch 2019-01 ver14: PrimeX

[Alexander Somov]

pull request indeed. . .
________________________________
From: Primexd <primexd-bounces at jlab.org> on behalf of Alexander Somov <somov at jlab.org>
Sent: Wednesday, December 9, 2020 9:41 PM
To: Alexander Austregesilo <aaustreg at jlab.org>; Igal Jaegle <ijaegle at jlab.org>; primexd at jlab.org <primexd at jlab.org>
Subject: Re: [Primexd] Monitoring Launch 2019-01 ver14: PrimeX

Hi Alex,

Thanks a lot Alex for processing these runs.

As I've mentioned, I updated a bunch of calibration constants
based on the this monitoring launch. Could you run it once again,
it should not take long, most files are on disc.

I've just added a few histograms to lumi_mon (there is a pool request),
please use this updated version.

I'll take a look on some of these job crashes later

Thanks,
             Sasha
________________________________
From: Alexander Austregesilo <aaustreg at jlab.org>
Sent: Tuesday, December 8, 2020 9:21 AM
To: Alexander Somov <somov at jlab.org>; Drew Smith <andrew.p.smith at duke.edu>; Igal Jaegle <ijaegle at jlab.org>
Cc: primexd at jlab.org <primexd at jlab.org>
Subject: Monitoring Launch 2019-01 ver14: PrimeX


Dear Colleagues,

We just completed a new monitoring launch over the 2019-01 PrimeX data set. We processed the first 5 files of 417 runs in the run range 61321 -  61956, selected with the RCDB query "@is_primex_production and @status_approved". The data was processed with a recent halld_recon version, but a few plugins created problems with the directory structure in the histogram file. This has been corrected now.

As usual, the 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/plotBrowser.py>
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_ver14/rootfiles/

The REST files, random trigger skims and several trees are saved on cache:
/cache/halld/offline_monitoring/RunPeriod-2019-01/ver14/REST/

We still observed about 20 crashes in the launch. Please find a list of the problematic log files below. Most of them are due to truncated input files, but the error message for files 061477_000, 061507_002, 061793_003 caught my eye:

JANA >>============================
JANA >> DL1MCTrigger: (brun)         --   line:281  /u/group/halld/Software/builds/Linux_CentOS7.7-x86_64-gcc4.8.5/jana/jana_0.8.2/Linux_CentOS7.7-x86_64-gcc4.8.5/include/JANA/JFactory.h
JANA >> DL1MCTrigger
JANA >> DTrigger: (evnt)             --   line:299  /u/group/halld/Software/builds/Linux_CentOS7.7-x86_64-gcc4.8.5/jana/jana_0.8.2/Linux_CentOS7.7-x86_64-gcc4.8.5/include/JANA/JFactory.h
JANA >> DTrigger
JANA >> JEventLoop:OneEvent  (evnt)  --   line:695  src/JANA/JEventLoop.cc
JANA >>----------------------------


Best regards,

Alex



------




/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061342/stdout.061342_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061349/stdout.061349_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061434/stdout.061434_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061477/stdout.061477_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061498/stdout.061498_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061506/stdout.061506_002.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061507/stdout.061507_002.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061517/stdout.061517_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061703/stdout.061703_001.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061704/stdout.061704_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061710/stdout.061710_000.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061717/stdout.061717_002.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061753/stdout.061753_001.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061779/stdout.061779_003.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061793/stdout.061793_003.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061794/stdout.061794_004.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061806/stdout.061806_002.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061879/stdout.061879_001.out
/work/halld2/data_monitoring/RunPeriod-2019-01/mon_ver14/log/061917/stdout.061917_003.out
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/primexd/attachments/20201210/52417101/attachment-0001.html>