Table Czar(s):

Alec Habig

Description:

This table is a distillation of the DCS_MAG_FAR and _NEAR tables. Those tables read out each minute and include all the thermocouple values, making too large to distribute to remote sites and too slow to load when one is doing data analysis. The BFLDDBICOILSTATE table records only the coil current and a status word, and only does so when there is a change of state (DeltaCurrent > 0.01A, or a significant gap in the data taking) or once per hour.

Usage in the offline software:

Could be used to check on an event-by-event basis how happy the magnetic fields are. Not relevant for MC data which have perfect coils. Not relevant for Caldet where there was no coil.

Validation for entering new data:

A happy magnet is auto-validated by the filling programs. An unhappy state (bad current, data gaps) will generate emails to the Table Czar, who will manually validate the problem and adjust the status codes as needed.

Process for automated filling:

Run as part of the normal DcsWriter process, which turns each Dcs root file into database tables when the root file is closed, twice per day.

Additional information:

The status byte will be zero if completely OK. The LSB is zero if there are problems but a human has judged things to be OK anyway. Further interpreting the bitmasks are done in the CoilStatus class, see that source.

Structure:

Updating status: