search

duartej / postproc-alibava

Utilities for post-processing data obtained with the ALIBAVA DAQ system.
0 stars 0 forks source link

Check possibility of reading files made with firmware < 2 #24

Closed duartej closed 6 years ago

duartej commented 6 years ago

Javi assures that it is possible to read out files created with the firmare version lower than 2 using the same logic than implemented right now @andregarciaa will check it.

andregarciaa commented 6 years ago

fortythieves does not allow data files taken with ALIBAVA firmware versions lower than 2. If the line 228 in IOAlibavaReader.cxx is commented, those versions are not rejected. Doing this:

1a

the result when executing again fortythieves with data taken with 0 firmware version, as RS 2017 for sensor M1-5 at -25C and -30V, is the following, where it can be appreciated that there is a problem with the calibration file (ignore "Not supported data version found (version=0<2). Data is not saved." messages):

1a

duartej commented 6 years ago

@andregarciaa please upload the files you used in your public directory at lxplus (in order to check and reproduce your problem)

andregarciaa commented 6 years ago

@duartej the three files can be found at my workspace/public directory. 2017-05-09_M1_5MBCERN-30V-25CcalRSON-90.8uA.cal 2017-05-09_M1_5MBCERN-30V-25CpedRSON-90.8uA.ped 2017-05-09_M1_5MBCERN-30V-25CRSON-90.8uA.dat

duartej commented 6 years ago

Just checking the processing of the pedestal and calibration files, you can see that nothing is processed:

$ fortythieves 2017-05-09_M1_5MBCERN-30V-25CpedRSON-90.8uA.ped -o $HOME/2017-05->09_M1_5MBCERN-30V-25CpedRSON-90.8uA.root IOAlibavaReader.read_data: Reading '2017-05-09_M1_5MBCERN-30V->25CpedRSON-90.8uA.ped', run number: -1 Not supported data version found (version=0<2). Data is not saved. Processing 0 from run -1 Processed 0 fortythieves INFO: Filling monitor plots CHIP[2][000%] Equivalent thing happen to the calibration.

So, it could be two things:

@andregarciaa could you check:

  1. that calibration and pedestals files actually contain events (ask Esteban or whoever pass you this files)
  2. ask Javi about the ability of his software to interpret firmware<2 calibrated and pedestal data
duartej commented 6 years ago

The problem is located in the alibava software choice of the time_t variable to store the data (first field of each file), which is platform dependent.