Updates Burn-in

[silviodonato]

Burn-in procedure updates for official v6 recipes

This issue tracks the remaining updates needed to align the BurnIn Controller workflow with the official v6 burn-in recipes.

Reference document:
QC_for_Preproduction_and_Production_v6.pdf

To do

• Align the burn-in cycles with the official recipes

  • Almost done, see:

    • standard_burnin_v6.txt which is generated by generate_standard_burnin_v6.py

  • Clarification requested from Alexander

• Fix the target temperatures during the tests:

  • Warm: 23°C, allowed range 20°C – 25°C
  • Cold: -34°C, allowed range -35°C – -33°C

• Read/check the temperature from /fnalbox/full/OW* instead of using only the nominal JULABO value

• Add a humidity check:

  The relative humidity should stay below 10%, and the dew point at least 5°C below target temperature.

• Check and update the IV scan configuration:

  For the IV curve use:
  0 V to -200 V in steps of 10 V
-200 V to -800 V in steps of 20 V
  The settling time before the current measurement is 1 s.
  Use a ramp speed of 10 V/s.

• Use the "balistic calibration"

See balistic_calibration.sh

• Use the new monitoring system during ramp-up and ramp-down

  • Start the process monitorOnly at the beginning of ramp-up/down
  • Terminate the process with SIGTERM at the end of ramp-up/down

  Possible implementation:

  • Add new steps:

    • addStep("monitoringOnly-START")
    • addStep("monitoringOnly-STOP")

  • Use these steps in standard_burnin_v6.txt/generate_standard_burnin_v6.py

• Use the new data produced by the monitoring system in the POTATO converter

  • Get an example from FNAL and use the new data in a similar way

[silviodonato]

-> update of default temperatures:
f014c61

-> take the average of the OW temperatures among active module as reference temperature during the burn-in:
1fafe1a
-> do not go the next step if the spread of OW temperatures is too large (the spread should get smaller with time)
609f354

[silviodonato]

• Use the new data produced by the monitoring system in the POTATO converter

In the central POTATOBurninFormatter.py, sensorTemperatureGraph is used to create SENSOR_Temperature in the IV test (sensorTemperatureDuringIV) (link).

In our implementation:

• sensorTemperatureGraph is taken from the DQM monitor file (link), then it is used to create sensorTemperatureDuringIV.
• the problem is that we don't have the data during the IV scan. And indeed we have this message when we run the code (see code):

--------------------------------------------------------------------
KNOWN ISSUE... we don't have the sensor temperature during IV
################################
WARNING: Reading value outside graph range: Graph 1748526379.0 Range(1748527204.0, 1748527478.0). Extrapolated value: 4.3555803298950195
################################
[...]
################################
WARNING: Reading value outside graph range: Graph 1748526721.0 Range(1748527204.0, 1748527478.0). Extrapolated value: 13.641585350036621
################################
getGraphValuesByTimestamp: Graph name:  Graph  N:  61  Start:  1748527204.0  Stop:  1748527478.0
KNOWN ISSUE... we don't have the sensor temperature during IV
--------------------------------------------------------------------

• using the new monitoring system we read the sensor data for all timestamps and solve this problem

[silviodonato]

[] Add a humidity check:

done
With 42312eb
in the burnin the target (or intermediate) temperature cannot be below the temperature corresponding to 10% of humidity nor below dewPoint -5C.
Note: To run a cold test (-34C) we need a dew point of -55C, previously we simply required required temp>dew point, ie. dew point > -34C. This means that we might need more time in the first cycle of the burnin to dry the air so strongly

[silviodonato]

[] Check and update the IV scan configuration:

Done:
pisaoutertracker/BurnIn_moduleTest@a0465c4
("Use a ramp speed of 10 V/s." was already done by default)