search

Mu2e / otsdaq_mu2e

Mu2e customizations for otsdaq
Other
1 stars 5 forks source link

artdaq: a file naming confusion in the middle of the run ? #61

Open pavel1murat opened 8 months ago

pavel1murat commented 8 months ago

I'm running a long data taking job in a configuration with a boardreader, an evenbuilder, and a datalogger (forgetting the dispatcher) and I'm observing that several hours into the run artdaq starts producing output files with malformed names, like the one below.

That apparently is self-recoverable - the last file written in the end of the run has its name formed properly. I'm observing that at the same time with https://github.com/Mu2e/otsdaq_mu2e/issues/60 , so the two problems could be related

I'm using the v2_07_00_e28_s126 bundle compiled in debug mode

-- regards, Pasha

  -rw-r--r--   1 mu2etrk  mu2e   86051551 Dec 19 13:51 raw.mu2e.trkvst.annex.105186_00000728.art
* -rw-r--r--   1 mu2etrk  mu2e  551386534 Dec 19 13:39 raw.mu2e.trkvst.annex.-_00000503.art
  -rw-r--r--   1 mu2etrk  mu2e  570132764 Dec 19 12:22 raw.mu2e.trkvst.annex.105186_00000291.art
  -rw-r--r--   1 mu2etrk  mu2e  572000352 Dec 19 11:02 raw.mu2e.trkvst.annex.105186_00000164.art
  -rw-r--r--   1 mu2etrk  mu2e  531352045 Dec 19 09:42 raw.mu2e.trkvst.annex.105186_00000001.art

the artdaq configuration is as follows: 

#------------------------------------------------------------------------------
#              label         host    port subsystem       allowed     prepend   target
#                                                        processors
#----------------------------------------------------------------------------
BoardReader : tracker_vst  localhost  -1      2              -1         none     none
EventBuilder: builder0     localhost  -1      2            "0-63"       none     none
DataLogger  : logger0      localhost  -1      2            "0-63"       none     none
Dispatcher  : dispatcher0  localhost  10500   2            "0-99"       none     none