alcap-org / AlcapDAQ

Alcap DAQ
alcap-org.github.io
8 stars 0 forks source link

Run 3732, DAQ livetime greater than 1 #59

Closed AndrewEdmonds11 closed 10 years ago

AndrewEdmonds11 commented 10 years ago

In run 3732 the DAQ livetime is greater than 1.

Debugging the code it seems that MDQ_DAQLivetime seems to be double inserting the gate length because alcapana is going through events twice:

TEST MESSAGE: Read 41 events from bank Na80 in event 1
TEST MESSAGE: Read 0 events from bank Na81 in event 1
TEST MESSAGE: Read 24 events from bank Na82 in event 1
TEST MESSAGE: Read 0 events from bank Na83 in event 1
TEST MESSAGE: Read 45 events from bank Nb80 in event 1
TEST MESSAGE: Read 2 events from bank Nb81 in event 1
TEST MESSAGE: Read 10 events from bank Nb82 in event 1
TEST MESSAGE: Read 0 events from bank Nb83 in event 1
TEST MESSAGE: Read 30 events from bank Nc82 in event 1
TEST MESSAGE: Read 0 events from bank Nc83 in event 1
TEST MESSAGE: Read 5 events from bank Nd82 in event 1
TEST MESSAGE: Read 0 events from bank Nd83 in event 1
TEST MESSAGE: Read 39 events from bank Ne82 in event 1
TEST MESSAGE: Read 0 events from bank Ne83 in event 1
TEST MESSAGE: Read 43 events from bank Nf81 in event 1
TEST MESSAGE: Read 1 events from bank Nf82 in event 1
TEST MESSAGE: Read 0 events from bank Nf83 in event 1
TEST MESSAGE: Read 33 events from bank Ng81 in event 1
TEST MESSAGE: Read 26 events from bank Ng82 in event 1
TEST MESSAGE: Read 0 events from bank Ng83 in event 1
TEST MESSAGE: Read 13 events from bank Nh81 in event 1
TEST MESSAGE: Read 37 events from bank Nh82 in event 1
TEST MESSAGE: Read 0 events from bank Nh83 in event 1
TEST MESSAGE: Read 184 events from bank CaUH in event 1
TEST MESSAGE: Read 184 events from bank CbUH in event 1
TEST MESSAGE: Read 687 events from bank CaBU in event 1
TEST MESSAGE: Read 687 events from bank CbBU in event 1
TEST MESSAGE: Read 687 events from bank CcBU in event 1
TEST MESSAGE: Read 687 events from bank CdBU in event 1
Event #1: Gate Length = 0.110000
TEST MESSAGE: Read 41 events from bank Na80 in event 1
TEST MESSAGE: Read 0 events from bank Na81 in event 1
TEST MESSAGE: Read 24 events from bank Na82 in event 1
TEST MESSAGE: Read 0 events from bank Na83 in event 1
TEST MESSAGE: Read 45 events from bank Nb80 in event 1
TEST MESSAGE: Read 2 events from bank Nb81 in event 1
TEST MESSAGE: Read 10 events from bank Nb82 in event 1
TEST MESSAGE: Read 0 events from bank Nb83 in event 1
TEST MESSAGE: Read 30 events from bank Nc82 in event 1
TEST MESSAGE: Read 0 events from bank Nc83 in event 1
TEST MESSAGE: Read 5 events from bank Nd82 in event 1
TEST MESSAGE: Read 0 events from bank Nd83 in event 1
TEST MESSAGE: Read 39 events from bank Ne82 in event 1
TEST MESSAGE: Read 0 events from bank Ne83 in event 1
TEST MESSAGE: Read 43 events from bank Nf81 in event 1
TEST MESSAGE: Read 1 events from bank Nf82 in event 1
TEST MESSAGE: Read 0 events from bank Nf83 in event 1
TEST MESSAGE: Read 33 events from bank Ng81 in event 1
TEST MESSAGE: Read 26 events from bank Ng82 in event 1
TEST MESSAGE: Read 0 events from bank Ng83 in event 1
TEST MESSAGE: Read 13 events from bank Nh81 in event 1
TEST MESSAGE: Read 37 events from bank Nh82 in event 1
TEST MESSAGE: Read 0 events from bank Nh83 in event 1
TEST MESSAGE: Read 184 events from bank CaUH in event 1
TEST MESSAGE: Read 184 events from bank CbUH in event 1
TEST MESSAGE: Read 687 events from bank CaBU in event 1
TEST MESSAGE: Read 687 events from bank CbBU in event 1
TEST MESSAGE: Read 687 events from bank CcBU in event 1
TEST MESSAGE: Read 687 events from bank CdBU in event 1
Event #1: Gate Length = 0.110000
Event #2: Gate Length = 0.110000
Event #2: Gate Length = 0.110000

This doesn't happen for run 3733 and in the beam report it seems that this run was directly after a CAEN recovery (which might also explain issue #58).

So I propose to scrap this run.

jrquirk commented 10 years ago

Let's remove this from the dataset. As soon as this is solidified in the code somewhere, we should close this issue. @AndrewEdmonds11 , I've assigned us to this because it'll be a production script one of us will probably write.

Edit: I can only assign one person to an issue. So @AndrewEdmonds11 , I choose you because you write all the production scripts.

AndrewEdmonds11 commented 10 years ago

Has this been solidified in the prodcution.db database, John?

jrquirk commented 10 years ago

This run has been absent from the datasets table for a while, I just forgot to close this.