Checklist for remote analysis shifts

If you have questions, problems, or findings regarding the remote analysis shift, write into the #remote.monitoring group on RocketChat

Step 2/3

format('Y'); $Day = $datetime->format('d')-1; $Month = $datetime->format('m'); $url = "http://katrin:tritium.Otten@2022@kdb.kaas.kit.edu/kdb-api.fcgi/json?run&system=fpd&from=".$Year."-".$Month."-".$Day; //call api $jsonData = file_get_contents($url); $json = array_values(json_decode($jsonData, true)); print("

Last run that has been added to kdb is run# ".end($json[1]['Run'])['Number']."

"); ?>

Please check the following parameters and values.
If any runs are effected, note down the run numbers in the comments and contact the corresponding system expert.

General information:

First run
Last run

Note: You can find the start and end time stamps of all runs in the kdb table.

Checks on webtrium:

Note: Make sure webtrium has been updated recently.

Parameter	What to look for	good (right/green) or bad (left/red)	Comment if bad
Endpoint Signal Background	Are there any jumps endpoint, signal, or background?

Checks on Adei:

Note: the timestamp on adei is giving in CET/CEST.

Subsystem	What to look for	good (right/green) or bad (left/red)	Comment if bad
High Voltage (K35/K65)	Are there any unexpected spikes in the K35/K65 readback. (more details can be found here)
High Voltage (absolute tank potential)	Are there any unexpected spikes in the tank potential readback. (more details can be found here)
BIXS	Is the BIXS signal stable? If not, something is wrong. Is there a long term trend visible?
Tritium throughput	Is the tritium throughput stable to within < 1 sccm? If not, something is wrong. Is there a long term trend visible?
FBM	Are there outliers in the FBM rate. Absolute values depend on pixel and KNMx period, keep in mind long term drift.
RW current and voltage	Were the IU scans performed roughly once per day (visible in the RW current and voltage (last week))?

Checks on brew:

A guide on how to use brew can be found here

If one of the columns doesn't exist in the latest brew table, mark the corresponding question as ok.

Parameter	What to look for	good (right/green) or bad (left/red)	Comment if bad
Run Length	Do any runs have shorter run length? Shorter length indicates missing subruns.
Data Size	Do any runs have a different data size? Smaller size indicates missing subruns.
FPD Energy Shift	Are there peaks in the FPD energy shift? Peaks in BREW plot of this value over time indicate rapid detector gain drifts, likely caused by large temperature changes of the building.
Grid-Sync Gap	Are there non-zero values in the grid-sync gap? Non-zero values indicate dead-time in DAQ.
U-MTD Deviation	Is the maximum deviation of U-MTD < 50 mV?
K35 Missing Points	Are there missing K35 values (> 5)? If there are runs with missing points, check the run individually (short subruns should have at least 10 points): KNM:
Rate 300eV	Is rate 300 eV comparable to other runs? (necessary for column density calculation).
Rate 90eV	Is rate 90 eV comparable to other runs? (necessary for column density calculation).
Tritium Purity	Is tritium purity estimated and around 98.6%? (necessary for column density calculation).
LARA Consistency Check	Are all entries in the LARA consistency check column ok?
Analysis monitoring	Manually mark the ckecked runs as good/bad in the "Analysis monitoring" column in the brew table.