Project

General

Profile

Bug #4581

run subrun numbers not updating in new output file renaming feature

Added by Michael Wang about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Category:
I/O
Target version:
Start date:
08/26/2013
Due date:
% Done:

100%

Estimated time:
1.00 h
Spent time:
Occurs In:
Scope:
Internal
Experiment:
DarkSide
SSI Package:
art
Duration:

Description

Kurt mentioned that the run # format specifiers in the new output file renaming feature in art do not change or update when a run is stopped and a new one started. I verified this myself for both run and subrun numbers:

-rw-r--r-- 1 mwang g163  83370659 Aug 26 11:04 ds50daq_r000101_sr01_20130826T160432.root
-rw-r--r-- 1 mwang g163  81832060 Aug 26 11:05 ds50daq_r000101_sr01_20130826T160451.root
-rw-r--r-- 1 mwang g163 102228805 Aug 26 11:07 ds50daq_r000101_sr01_20130826T160519.root
-rw-r--r-- 1 mwang g163  70416833 Aug 26 11:08 ds50daq_r000101_sr01_20130826T160753.root
-rw-r--r-- 1 mwang g163  54268120 Aug 26 11:09 ds50daq_r000101_sr01_20130826T160824.root

The sequence of commands associated with the output files above are:

  1. start run 101 (subrun1); stop run 101
  2. start run 102 (subrun1); stop run 102
  3. start run 103 (subrun1); pause run 103
  4. resume 103 (start subrun 2); pause run 103
  5. resume 103 (start subrun 3); pause run 103

The format specification we used is:

fileName = "ds50daq_r%06r_sr%02s_%to.root"

As you can see from the results above, the run and subrun numbers always remain at the initial ones -- 101 and 1, respectively -- and do not update when the new file is created upon the start of a new run/subrun.

Thanks,

Mike

Associated revisions

Revision 35745381 (diff)
Added by Christopher Green about 7 years ago

Test and fix for issue #4581

History

#1 Updated by Christopher Green about 7 years ago

  • Category set to I/O
  • Status changed from New to Assigned
  • Assignee set to Christopher Green
  • Target version set to 401
  • Estimated time set to 1.00 h
  • SSI Package art added
  • SSI Package deleted ()

We believe that it should be easy to reproduce this bug, and we further believe the fix is a one-liner.

#2 Updated by Christopher Green about 7 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Fix (and test for same) with 3574538

#3 Updated by Christopher Green about 7 years ago

  • Description updated (diff)

#4 Updated by Christopher Green about 7 years ago

  • Status changed from Resolved to Closed

#5 Updated by Christopher Green about 7 years ago

  • Target version changed from 401 to 1.08.09

Also available in: Atom PDF