Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jana will ask Patrick to back-up all data from the computers. Reference runs for data taking were not linked here because we are behind the firewall and it does not make sense to do all the work manually when the whole disk will be backed up.

 Note Note about tests:  There was a power on problem that we experienced several times after the CU had been off for a long time. This is When the CU is powered up and initialized after having been off for an extended period of time, trigger parity (and other data acquisition) errors are often observed for the first few hours of running.  This problem has been consistently observed over the life of the CU and is believed to be a DAQ issue (we dot not use Flight DAQ modules, nor FSW in the CU), not a CU problem, which has the consequence that it is not possible to power on the CU until the problem cure by itself, which normally happens in hours time scale. .  Consequently, some events taken within the first few hours after the CU is powered will show evidence of parity errors until the problem resolves on its own on the timescale of a few hours. The quality of the rest of the data is not adversely affected.  There has been some investigation on this from our team and Ric Claus, but we never came to a conclusion. Luca Latronico collected all the relevant info in some emails. Jana is aware of the issue and it's not really something that we need to fix because it's a transient problem that goes away. It seems not to have interfered with and agrees that due to the transient and non-fatal nature of the problem, it is a feature that does not need to be fixed.  Further investigation would involve swapping out the GASU and attaching the CU to a more flight-like DAQ, which is in line with the current plans for the unit.  This problem has not interfered with the operation of the CU in the past , so I expect it won't and it is not expected that it will interfere in the future. 

TKR
  • Noise and gain measurement (TkrNoiseAndGain.py)
    • Reference run for the TKR module attached to TEM 3: run 700004421 (PASSED)
    • Reference run for the TKR module attached to TEM 2: run 700004435 (PASSED*)

...