As of 14-Nov-2017, the pattern that is being used to name protoDUNE SP raw data files is the following:
- np04_raw_run%06r_%#_dl1.root
Other useful pieces of information are that raw data files are typically stored in
/nfs/sw/data
and the DataLogger is typically configured to switch files every 1000 events (or when the run changes). (I expect that the location for storing files will change once the data logging servers are available.)
The "%06r" substring is replaced by a minimum six digit run number. The "%#" is replaced with a file index that starts with "1" whenever the
dune-artdaq system is restarted and increments with each new file. This file index currently increments independent of run number (a feature that I suspect we would like to change). The "dl
" substring indicates which data logger wrote the file, in this case DataLogger #1.
To illustrate this pattern, here is a listing of recently-written raw data files:
[np04daq@np04-srv-010 /nfs/sw/data]$ ls -altF | head -25
total 2426527844
drwxrwxrwx 2 np04daq np-comp 270336 Nov 14 14:44 ./
-rw-r--r-- 1 np04daq np-comp 49911992 Nov 14 14:44 np04_raw_run000473_1_dl1.root
-rw-r--r-- 1 np04daq np-comp 41939393 Nov 14 13:40 np04_raw_run1000447_16_dl1.root
-rw-r--r-- 1 np04daq np-comp 41738380 Nov 14 13:33 np04_raw_run1000446_15_dl1.root
-rw-r--r-- 1 np04daq np-comp 42727997 Nov 14 13:26 np04_raw_run1000445_14_dl1.root
-rw-r--r-- 1 np04daq np-comp 42205102 Nov 14 13:19 np04_raw_run1000444_13_dl1.root
-rw-r--r-- 1 np04daq np-comp 44045740 Nov 14 13:11 np04_raw_run1000443_12_dl1.root
-rw-r--r-- 1 np04daq np-comp 60353745 Nov 14 13:03 np04_raw_run1000442_11_dl1.root
-rw-r--r-- 1 np04daq np-comp 97102368 Nov 14 12:53 np04_raw_run1000441_10_dl1.root
-rw-r--r-- 1 np04daq np-comp 185389107 Nov 14 12:43 np04_raw_run1000440_9_dl1.root
-rw-r--r-- 1 np04daq np-comp 147446048 Nov 14 12:32 np04_raw_run1000439_8_dl1.root
-rw-r--r-- 1 np04daq np-comp 84643132 Nov 14 12:13 np04_raw_run1000438_7_dl1.root
-rw-r--r-- 1 np04daq np-comp 62430312 Nov 14 12:04 np04_raw_run1000437_6_dl1.root
-rw-r--r-- 1 np04daq np-comp 42642471 Nov 14 11:56 np04_raw_run1000436_5_dl1.root
-rw-r--r-- 1 np04daq np-comp 41080519 Nov 14 11:46 np04_raw_run1000435_4_dl1.root
-rw-r--r-- 1 np04daq np-comp 41537367 Nov 14 11:34 np04_raw_run1000434_3_dl1.root
-rw-r--r-- 1 np04daq np-comp 41537367 Nov 14 11:24 np04_raw_run1000433_2_dl1.root
-rw-r--r-- 1 np04daq np-comp 154381439 Nov 14 10:58 np04_raw_run1000432_1_dl1.root
-rw-r--r-- 1 np04daq np-comp 452520 Nov 13 21:25 np04_raw_run1000431_1_dl1.root
-rw-r--r-- 1 np04daq np-comp 899848 Nov 13 21:22 np04_raw_run1000430_2_dl1.root
-rw-r--r-- 1 np04daq np-comp 4090741 Nov 13 21:21 np04_raw_run1000430_1_dl1.root
-rw-r--r-- 1 np04daq np-comp 447618 Nov 12 20:17 np04_raw_run1000429_1_dl1.root
-rw-r--r-- 1 np04daq np-comp 361680 Nov 11 00:30 np04_raw_run1000428_1_dl1.root
Files with run numbers greater than 1000000 were test runs taken without using the JCOP Run Control.
As we can see, the file index does not reset with each new run, rather it resets when the DAQ system is restarted (and as I say, I suspect that we should change this.) Looking at the list, we only see one run with two files (#1000430), so that appears to have been the only one in the observed time frame that had more than 1000 events.
Some suggestions that have been received/considered:
- add zero-padding to the index number in the file name so that it has fixed width
- reset the index number to "1" at the start of each run
- on this TWiki page, include a sample of the metadata files that are created on the DAQ disks to indicate that raw data files are ready to be copied downstream
-- KurtBiery - 2017-11-14