Project

General

Profile

Bug #25185

artdaq daq interface run sort based on timestamp can lead to bad behavior if folder timestamps are inadvertently changed

Added by Wesley Ketchum 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/10/2020
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

Just ran into this on ICARUS:

For some unknown reason the timestamp on one of the folders for an old run was changed, such that doing ls -lrth gave something like:

dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 13:47 3298
dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 14:17 3299
dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 14:47 3300
dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 15:15 3301
dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 15:30 3302
dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 15:34 3303
dr-xr-xr-x 2 icarus   E-1052 4.0K Nov 10 15:49 3304
dr-xrwxr-x 2 icarus   E-1052  225 Nov 10 16:35 1

When we try to start a new run then, DAQ interfaces wants it to be run number 2, which already exists, ergo ... no new run.

I don't know why that happened to the folder for run number 1 (clearly a separate issue), and I'm just speculating based on the observed problem that DAQInterface sorts the run records by time to determine the most recent one ... but if it does, perhaps it should do a true numerical sort instead? little but more coding, but perhaps worth it?

Also available in: Atom PDF