daq:readoutshell

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Severity ======
The ReadoutShell is the interface for experimenters in production mode and must catch if any of the devices doesn't record data properly.   

====== Problem ======
6/7/12 in the morning Dirk attempted to start another run (Run0066, logbook p.31). No settings were changed
nor touched. Readout mode was S800 send to GRETINA and GRETINA recording Mode3 only in TTCS (for LaBr coincidence). ReadoutShell gave proper feedback, but looking at the run directory only Global.dat was growing (S800 data), while GlobalRaw.dat (GRETINA mode 3 data) stayed empty.

====== Progress ======
(Dirk) On 6/8/12 same thing happened again. Actually geSave send data, most likely the one sent by NSCL DAQ. But GRETINA didn't validate any data. A stop/start fixed the issue, i.e. GRETINA did happily validate....

(Chris) ~9/3/12 Observations during e11017 indicate that Gretina is failing to validate due to a timestamp syncing issue.  Briefly, the timestamps of the digitizers are not reset during run start-up, but S800 receives an "IMP Sync" associated pulse, and the Gretina Trigger system timestamp was reset.  This problem may be observed offline by sending a Single IMP Sync; roughly 1 in 30 tries lead to this failure mode.  John Anderson at ANL has been informed and debugging will be attempted during the upcoming software working group meeting on 9/21-22.

Trace: • alarmresponse • detectors • replace_fuses_of_digitizer • decomp • mode3

Search

Toolbox

QR Code