Make a GBTStateTable attached to the indicated FITSTable
uses copy semantics
uses copy semantics
reattach this object to a new FITSTable. If there are problems with the file, the return value is False and appropriate warnings are sent to the logger. The resulting object is not attached to any FITSTable.
detach from any table.
Is this object attached to a FITSTable.
the STATE table converted to a table
the value of the MASTER keyword in this table
the value of the NUMPHASE keyword in this table
the value of the SWPERIOD keyword in this table
The SIGREF values - converted to the MS convention T if signal being observed, F if reference. In original FITS, 0 -> signal and 1 -> reference
The CAL values - converted to the MS convention T if CAL noise being observed, F if not. In original FITS, 0->no cal, 1->cal.
Digest an ACT_STATE table. Return False if one of the following rules are violated: 1) The changing columns must be either ICAL or ECAL and ISIGREF or ESIGREF. 2) Each row of STATE must have one and only one matching row in ACT_STATE. If the above are true, the return value will be true and mixedSignals will be False. states will contain the STATE row numbers corresponding to the rows of ACT_STATE (hence states will have the same number of elements as rows in ACT_STATE). For matching rows, the row number of the corresponding STATE row will appear in the location for that row in ACT_STATE (i.e. in order). ACT_STATE rows with no match in STATE will be indicated by a value of -1 at that location in states. Data corresponding to that ACT_STATE row should all be zero (not checked here, obviously). Hence states is resized so that it has the same number of rows as the ACT_STATE table. mixedSignals = T is not necessarily fatal. If multipleCal and multipleSigref are both false, that is okay. In that case, mixedSignals = True imples that there was a non-zero value in both an E and I column but not both *CAL or *SIGREF columns. If oldCalState is True, then this implies that the ECAL and ICAL columns in the ACT_STATE table have the wrong sense (i.e. 0->on and 1->off) instead of the sense in the STATE table (0->off and 1->on). It is expected that this will be fixed in a future version of the ACS FITS file. It is up to the GBTACSFiller class to decide how to set that argument.