Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1488

News	FAQ
Search	Home

gbtmsfiller.status - Function

	Package	nrao
	Module	gbt
	Tool	gbtmsfiller

Report the status of the filler

Synopsis
status()

Returns
record

Description
Returns the status record.

status - Record	the status record
status.attached	is the filler attached
	Allowed: boolean
status.nextscan	pending scan number to be processed
	Allowed: integer
status.nextdmjd	pending DMJD value to be processed
	Allowed: double
status.nexttimestamp	pending scan timestamp to be processed
	Allowed: double
status.project	project being filled
	Allowed: string
status.msdirectory	The directory where any MSs are being written
	Allowed: string
status.object	object constraint
	Allowed: string
status.mintime	minimum time constraint
	Allowed: string
status.maxtime	maximum time constraint
	Allowed: string
status.minscan	minimum scan number constraint
	Allowed: integer
status.maxscan	maximum scan number constraint
	Allowed: integer
status.fillrawpointing	Are the raw pointings being saved?
	Allowed: boolean
status.fillrawfocus	Are the raw focus data being saved?
	Allowed: boolean
status.filllags	Are the raw lags being filled?
	Allowed: boolean
status.vv	The current vanVleck correction
	Allowed: string
status.smooth	The current smoothing function
	Allowed: string
status.usehighcal	Is the HIGHCAL being used? (old data only)
	Allowed: boolean
status.compresscalcols	Are the spectral line calibration columns compressed?
	Allowed: boolean
status.usebias	Is the bias being calculated for the ACS vanVleck correction?
	Allowed: boolean
status.backendtype	backend type constraint
	Allowed: string
status.oneacsms	Is a single ACS MS being filled?
	Allowed: boolean
status.dcbias	Current DC bias value.
	Allowed: double
status.minbiasfactor	Minimum bias factor.
	Allowed: integer
status.fixlags	Try and fix the ACS lags.
	Allowed: boolean
status.dcr	Status of the MS being filled with DCR data
	Allowed: backend status record
status.holo	Status of the MS being filled with Holography data
	Allowed: backend status record
status.sp	Status of the MS being filled with SpectralProcessor data
	Allowed: backend status record
status.acs	Record of status records for ACS (spectrometer) data
	Allowed: record

The ACS (spectrometer) status record has the following structure:

acs - Record	Record of status records for ACS data
acs.ABCD	Status of the MS being filled with all ACS data (banks A,B,C,D)
	Allowed: backend status record
acs.A	Status of the MS being filled with bank A ACS data
	Allowed: backend status record
acs.B	Status of the MS being filled with bank B ACS data
	Allowed: backend status record
acs.C	Status of the MS being filled with bank C ACS data
	Allowed: backend status record
acs.D	Status of the MS being filled with bank D ACS data
	Allowed: backend status record

Each backend has a status record (the ACS (spectrometer) backend has 5 status records, one for the single MS being filled with data from all banks and one for each possible bank, all grouped in the acs record). The backend status record looks like this:

backend status - Record	the backend status record
backend status.ms	The name of the MS being filled. This is unset if it is not being filled.
	Allowed: string
backend status.nrows	The total number of rows in that MS. This is -1 if it is not being filled.
	Allowed: integer

If the attached field is False, all of the other fields may not reflect the true state of the filler. The project, object, mintime, maxtime, minscan, maxscan, fillrawpointing, fillrawfocus, filllags, vv, smooth, usehighcal, compresscalcols, usebias, oneacsms and backendtype constraints can all be set via this DO interface. When the filler is at the end of the scan log (more() return False) then nextscan will have a value of -1 and nextdmjd and nextimestamp will have values of 0.0.