Scan Coordinator (sc)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| sc.nextscannumber |
|
The Next Scan Number allows you to set the scan number to a new value for the next scan executed. |
sc.projid |
|
The Project ID is the number assigned to your program on the telescope schedule, e.g., B345. This string is used as a directory name for your data. The Project ID must be < 16 characters long. |
sc.sourcename |
|
Any Source Name less than 32 characters. In pulsar observing this name is used to fetch the current pulsar timing parameters and must be in a standard 'hhmmsdd' format, e.g., 0329+54. In other observing modes the Source Name is only an identifier label. |
sc.scanid |
|
The Scan I.D. is a supplement to the Source Name for labeling the data. It has no effect on the data taking process. The string must be less than 32 characters. |
sc.scanlength |
|
The Scan Length is the duration of the scan in seconds. Any data integrations completed after the end of a scan will normally be discarded. Hence, the Scan Length is typically an integer number of integration times plus a second or two. |
sc.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
sc.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
sc.observername |
|
The Observer's Name can be any string. This is recorded with the data. |
sc.logfile |
|
Glish Log File is the name of the file that records all glish language commands generated by 'GBT Observe', either from GUI selections and entries, from the command line, or from observing table execution |
sc.iardstype |
Pointing, "Spectral Line", N/A |
Iards Type determines the type of real time display to be activated. |
sc.obsmode |
"Spectral Line", Continuum, "Pulsar Timing", "Pulsar Search", "Pulsar Monitoring", "Pulsar Dedispersion", "Pulsar Voltage Sampling", N/A |
obs_mode defines the current observing mode. |
sc.obstype |
Continuum, "Spectral Line (SPM)", "Pulsar Timing (SPM)", "Pulsar Search (SPM)", "Spectral Line (SP)", "Pulsar Timing (SP)", "Pulsar Dedispersion", "Pulsar Search (BCPM)", "Pulsar Voltage Sampling (BCPM)", "Pulsar Timing (BCPM)", "Pulsar Monitoring (BCPM)" |
Observing Type determines the parameters requested on the left side of the Main Screen and selects the primary backend to be used. It also sets a lot of default values for various devices. Make this selection before setting parameters for specific devices. |
sc.switchingsignalsmaster |
SpectralProcessor, DCR, Spectrometer |
The Switching Signals Master selects which backend provides the switching signals to all of the backends. |
sc.calstate |
Off, On |
Each Cal toggle button specifies the state of the receiver calibration signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the Cal states are predetermined by the selected mode. |
sc.sigrefstate |
Sig, Ref |
Each SigRef toggle button specifies the state of the receiver frequency/load/beam switch signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the SigRef states are predetermined by the selected mode. |
sc.blankingtime |
|
Banking Time is the time in seconds at the beginning of each switch phase when data integration is inhibited. The Blanking Time may be set to a different value for each phase through the glish command line, but one value is usually sufficient for every phase, and that value is specified here. The resolution in 100nS. |
sc.numberofphases |
|
The Number of Phases specifies how many phases are in the switching cycle. This number is predetermined by the selected Switching Mode for all but the "User Defined" mode. In that mode the number may be between 1 and 10. |
sc.phasestart |
|
Each Phase Start entry field specifies the beginning of this phase as a fraction of the total switch cycle. The first start time must be zero, they must increase monotonically, and the last phase start time must be less than one. The effective integration time for a phase in one switching cycle is the product of the Switch Period and the difference between that phase's and the next phase's start times minus the Blanking Time. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the phase Start times are predetermined by the selected mode. |
sc.switchmode |
"Total Power", "Total Power, No Cal", "Total Power, Spec Proc", "Freq Switch, 01", "Freq Switch, 12", "Freq Switch, 0102", "Freq Switch, User Def.", "Beam Switch", "Beam Switch, User Def.", "Pol. Switch", "Pol. Switch, User Def.", "User Defined" |
The Switching Mode is a menu of predefined switching modes plus a user-defined mode. The switching parameters may be displayed with the Switching Setup button. The Number of Phases, SigRef and Cal states, phase Start times, and Advance Sig selections are all set when one of the predefined modes is selected. In the "User Defined" mode all of these parameters are available for user input. |
sc.bandwidth |
|
The bandwidth in MHz desired for the observation. The valueof this parameter depends on the backend selected.
*** This parameter is currently not functionally implemented. *** |
sc.subsystemselect |
|
The Subsystem Select parameters determines which of the GBT subsystems are active to participate in scan sequence. Normally, this parameter is set automatically as a result of selection of the receiver and observing type. The value for this parameter is a 19-element, boolean array with the elements corresponding, respectively, to the Antenna, LO1, 0.3-0.9 GHz Rcvr, 1.2-1.7 GHz Rcvr, 1.7-2.6 GHz Rcvr, 3.9-5.8 GHz Rcvr, 8-10 GHz Rcvr, 12-15 GHz Rcvr, 18-26 GHz Rcvr, I.F. Rack, Converter Rack, Analog Filter Rack, Switching Signal Selector, Spectral Processor, Digital Continuum Rcvr, Holography, Spectrometer, Archivist, and I.F. Manager. |
sc.receiver |
NoiseSource, "0.290 - 0.395", "0.385 - 0.520", "0.510 - 0.690", "0.680 - 0.920", "0.910 - 1.230", "1.15 - 1.73", "1.73 - 2.60", "3.95 - 5.85", "8.00 - 10.1", "12.0 - 15.4", "18.0 - 22.4", "22.0 - 26.5", "40.0 - 50.0" |
The Receiver parameter, in conjunction with the Observing Type, determines a lot of default settings the setup up the GBT system to use the selected receiver. Make this selection before setting parameters for specific devices. |
sc.scannumber |
|
The Scan Number normally updates at the beginning of each scan, but it may be reset by specifying a new value for nextscannumber. The Scan Number itself is read only. |
|
Procedure (proc)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| proc.startutc |
|
Start UTC is a parameter that allows you to start a procedure at a specified Universal Coordinated Time rather than just as soon as possible. The time is assumed to be within the day starting 1/2 hour before and ending 23 1/2 hours after the current time. The start time is valid for one scan only and is cleared after a scan is initiated. Procedures that run more than one scan will start all scans after the first one a.s.a.p. Subsequent procedure will also start a.s.a.p. unless a new start time is specified before each is invoked. This parameter is assigned as a string in sexagesimal format, 'HH:MM:SS.s' |
proc.startlst |
|
Start LST is a parameter that allows you to start a procedure at a specified Local Apparent Sidereal Time rather than just as soon as possible. The time is assumed to be within the day starting 1/2 hour before and ending 23 1/2 hours after the current time. The start time is valid for one scan only and is cleared after a scan is initiated. Procedures that run more than one scan will start all scans after the first one a.s.a.p. Subsequent procedure will also start a.s.a.p. unless a new start time is specified before each is invoked. This parameter is assigned as a string in sexagesimal format, 'HH:MM:SS.s' |
proc.stoputc |
|
Stop UTC is a parameter that allows you to stop the first scan of a procedure at a specified Universal Coordinated Time. The scan is started as soon as possible. The Stop UTC is generally useful with the 'track' procedure where one wants to start tracking an object as soon as possible while being guaranteed that the telescope will move to the next source at the specified time. This is often useful for VLBI observations. The time is assumed to be within the day starting 1/2 hour before and ending 23 1/2 hours after the current time. The stop time is valid for one scan only and is cleared after a scan is initiated. This parameter is assigned as a string in sexagesimal format, 'HH:MM:SS.s' |
proc.stoplst |
|
Stop LST is a parameter that allows you to stop the 'track' procedure at a specified Local Apparent Sidereal Time. The scan is started as soon as possible. The Stop LST is generally useful when one wants to start tracking an object as soon as possible while being guaranteed that the telescope will move to the next source at the specified time. This is often useful for VLBI observations. The time is assumed to be within the day starting 1/2 hour before and ending 23 1/2 hours after the current time. The stop time is valid for one scan only and is cleared after a scan is initiated. This parameter is assigned as a string in sexagesimal format, 'HH:MM:SS.s' |
proc.scanduration |
|
Scan Duration is the length of the 'track' procedure scan in UTC seconds. Any data integrations completed after the end of a scan will normally be discarded. Hence, the Scan Duration is typically an integer number of integration times plus a second or two. |
proc.pointduration |
|
Point Integration is the integration time, in seconds, spent on each location of a map grid or a five-point pointing procedure. |
proc.onduration |
|
The On Integration is the integration time, in seconds, spent on each location of an off-on-off observing procedure. |
proc.offduration |
|
The Off Integration is the integration time, in seconds, spent on each off observation. |
proc.offinterval |
|
Off Interval specifies the number of locations in a Point-Map that are integrated before making an "off" integration outside the map area. For a RALongMap or DecLatMap Off Interval specifies the number of rows of the map to be made between "off" observations. |
proc.backandforth |
Yes, No |
Back&Forth selects whether or not alternate sweeps in a raster scan map are traced in opposite directions. By selecting "yes" you save time by not having the telescope retrace to the same side of the map for each sweep. |
proc.separatescans |
Yes, No |
Separate Scans specifies whether each integration in an on-off or five-point procedure is recorded as a separate scan with different scan numbers. |
proc.symmetric |
Yes, No |
If symmetric is set to yes then the nod procedure observes the 1st beam, 2nd beam, 2nd beam, 1st beam using four scans. If symmetric is set to no then the nod procedure observes the 1st beam and then the 2nd beam using two scans. |
proc.onbeam |
1, 2, 3, 4 |
onbeam specifies which beam is to be used for the first scan in the nod procedure |
proc.data |
Yes, No |
The Record Data button selects whether data are recorded during a scan. The data might be temporarily turned off to make a trial run of a procedure to test the telescope motions. This is a spring-loaded value in the sense that it returns to "on" at the end of each scan. |
proc.startnumber |
|
Start Number allows you to resume a partially completed Cross, raster map, or Point-Map by specifying the sweep or point number to start with. |
proc.repeatnumber |
|
Repeats specifies the number of times the procedure is to be repeated with the same parameter values. |
proc.numsweeps |
|
Number of Sweeps specifies the number of sweeps in a raster map. An odd number of sweeps will run the center sweep through the specified map center position. An equal number of sweeps will be made on either side of the center position. |
proc.radius |
|
This parameter specifies the Radius, in arcminutes, of the circle traced by the Circle procedure |
proc.startangle |
|
Start Angle specifies the parallactic angle, in degrees, for the beginning of the trace in the Circle procedure. Zero degrees is north; 90 degrees is east. |
proc.angularrate |
|
Angular Rate specifies the rate of scan, in degrees per minute, along the circle in the Circle procedure. |
proc.ra |
|
R.A. is the right ascension, in HH:MM:SS.SS format, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.ha |
|
H.A. is the hour angle, in HH:MM:SS.SS format, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.dec |
|
Dec. is the declination, in sDD:MM:SS.S format, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.long |
|
This parameter is the galactic Longitude, in decimal degrees, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.lat |
|
This parameter is the galactic Latitude, in decimal degrees, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.az |
|
This parameter is the Azimuth, in decimal degrees, at the beginning of the Track procedure or the center of a map, Cross, or Circle. Azimuth is 0.0 degrees at north and +90.0 degrees at east. |
proc.elev |
|
This parameter is the Elevation, in decimal degrees, at the beginning of the Track procedure or the center of a map, Cross, or Circle. The minimum elevation of the GBT is 5 degrees. |
proc.startelev |
|
This parameter specifies the Start Elevation, in degrees, of a Tipping scan. The start and stop elevations determine the direction of scan, and the sign of the scan rate is ignored. |
proc.stopelev |
|
This parameter specifies the Stop Elevation, in degrees, of a Tipping scan. The start and stop elevations determine the direction of scan, and the sign of the scan rate is ignored. |
proc.udlong |
|
This parameter is the Longitude in "User Defined" coordinates, in decimal degrees, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.udlat |
|
This parameter is the Latitude in "User Defined" coordinates, in decimal degrees, at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.sslong |
|
This parameter is the Longitude, in decimal degrees, in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. This longitude is at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.sslat |
|
This parameter is the Latitude, in decimal degrees, in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. This latitude is at the beginning of the Track procedure or the center of a map, Cross, or Circle. |
proc.rarate |
|
R.A. Rate is the right ascension rate, in arcminutes per minute, of the telescope motion in the Track, map, or Cross procedure. |
proc.harate |
|
H.A. Rate is the hour angle rate, in arcminutes per minute, of the telescope motion in the Track, map, or Cross procedure. |
proc.decrate |
|
Dec. Rate is the declination rate, in arcminutes per minute, of the telescope motion in the Track, map, or Cross procedure. |
proc.longrate |
|
This parameter is the galactic Longitude Rate, in arcminutes per minute, of the telescope motion in the Track, map, or Cross procedure. |
proc.latrate |
|
This parameter is the galactic Latitude Rate, in arcminutes per minute, of the telescope motion in the Track, map, or Cross procedure. |
proc.azrate |
|
This parameter is the Azimuth Rate, in arcminutes per minute, of the telescope motion in the Track, map, or Cross procedure. |
proc.elevrate |
|
This parameter is the Elevation Rate, in arcminutes per minute, of the telescope motion in the Track, map, Cross, or Tipping procedure. |
proc.udlongrate |
|
This parameter is the Longitude Rate, in arcminutes per minute, in "User Defined" spherical coordinates. This is the rate of telescope motion in the Track, map, or Cross procedure. |
proc.udlatrate |
|
This parameter is the Latitude Rate, in arcminutes per minute, in "User Defined" spherical coordinates. This is the rate of telescope motion in the Track, map, or Cross procedure. |
proc.sslongrate |
|
This parameter is the Longitude Rate, in arcminutes per minute, in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. This is the rate of telescope motion in the Track, map, or Cross procedure. |
proc.sslatrate |
|
This parameter is the Latitude Rate, in arcminutes per minute, in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. This is the rate of telescope motion in the Track, map, or Cross procedure. |
proc.ralength |
|
R.A. Length is the full length, in arcminutes, of a right ascension sweep in a Cross or map procedure. The sweep is centered on the specified R.A. coordinate. |
proc.halength |
|
H.A. Length is the full length, in arcminutes, of a hour angle sweep in a Cross or map procedure. The sweep is centered on the specified R.A. coordinate. |
proc.declength |
|
Dec. Length is the full length, in arcminutes, of a declination sweep in a Cross or map procedure. The sweep is centered on the specified Dec. coordinate. |
proc.longlength |
|
Long. Length is the full length, in arcminutes, of a galactic longitude sweep in a Cross or map procedure. The sweep is centered on the specified longitude coordinate. |
proc.latlength |
|
Lat. Length is the full length, in arcminutes, of a galactic latitude sweep in a Cross or map procedure. The sweep is centered on the specified latitude coordinate. |
proc.azlength |
|
Az. Length is the full length, in arcminutes, of an azimuth sweep in a Cross or map procedure. The sweep is centered on the specified azimuth coordinate. |
proc.elevlength |
|
Elev. Length is the full length, in arcminutes, of an elevation sweep in a Cross or map procedure. The sweep is centered on the specified elevation coordinate. |
proc.udlonglength |
|
Long. Length is the full length, in arcminutes, of a longitude sweep in "User Defined" coordinates in a Cross or map procedure. The sweep is centered on the specified longitude coordinate. |
proc.udlatlength |
|
Lat. Length is the full length, in arcminutes, of a latitude sweep in "User Defined" coordinates in a Cross or map procedure. The sweep is centered on the specified latitude coordinate. |
proc.sslonglength |
|
Long. Length is the full length, in arcminutes, of a longitude sweep in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. The sweep is centered on the specified longitude coordinate in a Cross or map procedure. |
proc.sslatlength |
|
Lat. Length is the full length, in arcminutes, of a latitude sweep in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. The sweep is centered on the specified latitude coordinate in a Cross or map procedure. |
proc.rastep |
|
R.A. Step is the right ascension step size, in arcminutes, between declination sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or rows of point locations are centered on the specified R.A. coordinate. |
proc.hastep |
|
H.A. Step is the hour angle step size, in arcminutes, between declination sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or rows of point locations are centered on the specified H.A. coordinate. |
proc.decstep |
|
Dec. Step is the declination step size, in arcminutes, between right ascension or hour angle sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or columns of point locations are centered on the specified Dec. coordinate. |
proc.longstep |
|
Long. Step is the galactic longitude step size, in arcminutes, between latitude sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or rows of point locations are centered on the specified longitude coordinate. |
proc.latstep |
|
Lat. Step is the galactic latitude step size, in arcminutes, between longitude sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or columns of point locations are centered on the specified latitude coordinate. |
proc.azstep |
|
Az. Step is the azimuth step size, in arcminutes, between elevation sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or rows of point locations are centered on the specified azimuth coordinate. |
proc.elevstep |
|
Elev. Step is the elevation step size, in arcminutes, between azimuth sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or columns of point locations are centered on the specified elevation coordinate. |
proc.udlongstep |
|
Long. Step is the longitude step size, in arcminutes, between latitude sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or rows of point locations are centered on the specified "User Defined" longitude coordinate. |
proc.udlatstep |
|
Lat. Step is the latitude step size, in arcminutes, between longitude sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or columns of point locations are centered on the specified "User Defined" latitude coordinate. |
proc.sslongstep |
|
Long. Step is the longitude step size, in arcminutes, between latitude sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or rows of point locations are centered on the specified longitude in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. |
proc.sslatstep |
|
Lat. Step is the latitude step size, in arcminutes, between longitude sweeps in a raster map or between locations in a Point-Map procedure. The sweeps or columns of point locations are centered on the specified latitude in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. |
proc.rapoints |
|
#R.A. Points specifies the number of Point-Map procedure locations in the right ascension coordinate. An odd number will put the center column on the specified R.A. coordinate. |
proc.hapoints |
|
#H.A. Points specifies the number of Point-Map procedure locations in the hour angle coordinate. An odd number will put the center column on the specified H.A. coordinate. |
proc.decpoints |
|
#Dec. Points specifies the number of Point-Map procedure locations in the declination coordinate. An odd number will put the center row on the specified Dec. coordinate. |
proc.longpoints |
|
#Lon. Points specifies the number of Point-Map procedure locations in the galactic longitude coordinate. An odd number will put the center column on the specified longitude coordinate. |
proc.latpoints |
|
#Lat. Points specifies the number of Point-Map procedure locations in the galactic latitude coordinate. An odd number will put the center row on the specified latitude coordinate. |
proc.azpoints |
|
#Az. Points specifies the number of Point-Map procedure locations in the azimuth coordinate. An odd number will put the center column on the specified azimuth coordinate. |
proc.elevpoints |
|
#El. Points specifies the number of Point-Map procedure locations in the elevation coordinate. An odd number will put the center row on the specified elevation coordinate. |
proc.udlongpoints |
|
#Lon. Points specifies the number of Point-Map procedure locations in the "User Defined" longitude coordinate. An odd number will put the center column on the specified longitude coordinate. |
proc.udlatpoints |
|
#Lat. Points specifies the number of Point-Map procedure locations in the "User Defined" latitude coordinate. An odd number will put the center row on the specified latitude coordinate. |
proc.sslongpoints |
|
#Lon. Points specifies the number of Point-Map procedure locations in the longitude of spherical coordinates whose equator and prime meridian are tracking a specified solar system object. An odd number will put the center column on the specified longitude coordinate. |
proc.sslatpoints |
|
#Lat. Points specifies the number of Point-Map procedure locations in the latitude of spherical coordinates whose equator and prime meridian are tracking a specified solar system object. An odd number will put the center row on the specified latitude coordinate. |
proc.raoffset |
|
R.A. Offset is the right ascension offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. |
proc.haoffset |
|
H.A. Offset is the hour angle offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. |
proc.decoffset |
|
Dec. Offset is the declination offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. The epoch of this coordinate is set by the Coordinate Mode as J2000, B1950, or Current RA/Dec. |
proc.longoffset |
|
Long. Offset is the galactic longitude offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or two of the locations in a Five-Point procedure. |
proc.latoffset |
|
Lat. Offset is the galactic latitude offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or two of the locations in a Five-Point procedure. |
proc.azoffset |
|
Az. Offset is the azimuth offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or two of the locations in a Five-Point procedure. It is also used as an azimuth offset in the Five-Point procedure when working in a coordinate system other than Azimuth/Elevation. |
proc.elevoffset |
|
Elev. Offset is the elevation offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or two of the locations in a Five-Point procedure. |
proc.udlongoffset |
|
Long. Offset is the "User Defined" longitude offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. |
proc.udlatoffset |
|
Lat. Offset is the "User Defined" latitude offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. |
proc.sslongoffset |
|
Long. Offset is the longitude offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. In this case, longitude is defined in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. |
proc.sslatoffset |
|
Lat. Offset is the latitude offset, in arcminutes, of the "off" or reference location for the Point-Map or On-Off procedure or for two of the locations in a Five-Point procedure. In this case, latitude is defined in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. |
proc.secantdec |
Yes, No |
The secant(dec) selection determines whether right ascension or hour angle offsets and sweep lengths are multiplied by the secant of the declination to determine the actual offsets or lengths on the sky. If secant(dec) is 'no', the offsets are small circle arc lengths. If secant(dec) is 'yes', the offsets are great circle arc lengths. |
proc.secantelev |
Yes, No |
The secant(elev) selection determines whether azimuth offsets and sweep lengths are multiplied by the secant of the elevation to determine the actual offsets or lengths on the sky. If secant(elev) is 'no', the offsets are small circle arc lengths. If secant(elev) is 'yes', the offsets are great circle arc lengths. |
proc.secantlat |
Yes, No |
The secant(lat) selection determines whether galactic longitude offsets and sweep lengths are multiplied by the secant of the latitude to determine the actual offsets or lengths on the sky. If secant(lat) is 'no', the offsets are small circle arc lengths. If secant(lat) is 'yes', the offsets are great circle arc lengths. |
proc.secantudlat |
Yes, No |
The secant(lat) selection determines whether "User Defined" longitude offsets and sweep lengths are multiplied by the secant of the latitude to determine the actual offsets or lengths on the sky. If secant(lat) is 'no', the offsets are small circle arc lengths. If secant(lat) is 'yes', the offsets are great circle arc lengths. |
proc.secantsslat |
Yes, No |
The secant(lat) selection determines whether longitude offsets and sweep lengths are multiplied by the secant of the latitude to determine the actual offsets or lengths on the sky. In this case, latitude is defined in spherical coordinates whose equator and prime meridian are tracking a specified solar system object. If secant(lat) is 'no', the offsets are small circle arc lengths. If secant(lat) is 'yes', the offsets are great circle arc lengths. |
proc.autoupdatelpc |
Yes, No |
This parameter specifies whether automatic updating of the LPC values determined from AIPS++ is to be used or whether the values must be accepted or rejected based on observers reply. |
proc.realtimedisplay |
Yes, No |
This parameter specifies which real time display is selected or if the real time display is off. |
proc.startfocus |
|
This parameter specifies the Start Focus position, in millimeters, of a Focus scan. The start and stop positions determine the direction of scan, and the sign of the Focus Rate is ignored. |
proc.stopfocus |
|
This parameter specifies the Stop Focus position, in millimeters, of a Focus Prime procedure. The start and stop positions determine the direction of scan, and the sign of the Focus Rate is ignored. |
proc.focusrate |
|
This parameter is the Focus Rate, in millimeters per minute, of the prime focus receiver in the Focus Prime procedure. The start and stop positions determine the direction of scan, and the sign of the Focus Rate is ignored. |
proc.startrotation |
|
This parameter specifies the Start Rotation position, in degrees, of a prime focus receiver rotation scan. |
proc.stoprotation |
|
This parameter specifies the Stop Rotation position, in degrees, of a prime focus receiver rotation scan. |
proc.rotationrate |
|
This parameter is the Rotation Rate, in degrees per minute, of the prime focus receiver. |
proc.primefocusaxial |
|
This parameter is the axial position of the prime focus receiver box in meters. This motion is along a line from roughly the center of the reflecting surface through the prime focus point with positive motion being away from the dish. If the focus tracking mode is on, this position is with respect to the nominally optimum box position for the current elevation. If focus tracking is off, the offset is with respect to the optimum box position at the telescope rigging elevation. |
proc.primefocusaxialrate |
|
This parameter is the axial velocity of the prime focus receiver box in meters per second. The box begins its motion at the beginning of a scan at the position specified by the parameter 'primefocusaxial'. Positive motion is away from the dish. |
proc.primefocusrotation |
|
This parameter is the rotational position of the prime focus receiver box in degrees. |
proc.primefocusrotationrate |
|
This parameter is the rotational velocity of the prime focus receiver box in degrees per second. The box begins its motion at the beginning of a scan at the position specified by the parameter 'primefocusrotation'. |
proc.primefocustranslation |
|
This parameter is the translational offset of the prime focus box in meters. Box translation is in the plane of symmetry of the antenna, perpendicular to the axial focus axis, with positive motion being away from the feed support arm. If the focus tracking mode is on, this offset is with respect to the nominally optimum box position for the current elevation. If focus tracking is off, the offset is with respect to the optimum box position at the telescope rigging elevation. |
proc.primefocustranslationrate |
|
This parameter is the translational velocity of the prime focus box in meters per second. The box begins its motion at the beginning of a scan at the position specified by the parameter 'primefocustranslation'. Box translation is in the plane of symmetry of the antenna, perpendicular to the axial focus axis, with positive motion being away from the feed support arm. |
proc.subreflectorx |
|
This parameter is the X coordinate offset of the subreflector in meters. If the focus tracking mode is on, this offset is with respect to the nominally optimum subreflector position for the current elevation. If focus tracking is off, the offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorxrate |
|
This parameter is the X coordinate offset velocity of the subreflector in meters per second. The subreflector begins its motion at the beginning of a scan at the position specified by the parameter 'subreflectorx'. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorxstart |
|
This parameter is the start position of the X coordinate offset of the subreflector in meters. The offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorxstop |
|
This parameter is the stop position of the X coordinate offset of the subreflector in meters. The offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorxstep |
|
This parameter is the X coordinate offset step of the subreflector in the X direction in milliters. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectory |
|
This parameter is the Y coordinate offset of the subreflector in meters. If the focus tracking mode is on, this offset is with respect to the nominally optimum subreflector position for the current elevation. If focus tracking is off, the offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectoryrate |
|
This parameter is the Y coordinate offset velocity of the subreflector in meters per second. The subreflector begins its motion at the beginning of a scan at the position specified by the parameter 'subreflectory'. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorystart |
|
This parameter is the start position of the Y coordinate offset of the subreflector in meters. The offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorystop |
|
This parameter is the stop position of the Y coordinate offset of the subreflector in meters. The offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorystep |
|
This parameter is the Y coordinate offset step of the subreflector in the X direction in milliters. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorz |
|
This parameter is the Z coordinate offset of the subreflector in meters. If the focus tracking mode is on, this offset is with respect to the nominally optimum subreflector position for the current elevation. If focus tracking is off, the offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorzrate |
|
This parameter is the Z coordinate offset velocity of the subreflector in meters per second. The subreflector begins its motion at the beginning of a scan at the position specified by the parameter 'subreflectorz'. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorzstart |
|
This parameter is the start position of the Z coordinate offset of the subreflector in meters. The offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorzstop |
|
This parameter is the stop position of the Z coordinate offset of the subreflector in meters. The offset is with respect to the optimum position at the telescope rigging elevation. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectorzstep |
|
This parameter is the Z coordinate offset step of the subreflector in the X direction in milliters. The X,Y,Z axes are defined as a right-hand coordinate system with Y away from the dish, X in the plane of away from the feed arm, and Z normal to the plane of symmetry. |
proc.subreflectoracty1 |
|
This parameter is the position of subreflector actuator Y1 in meters. Increasing Y actuator length moves the subreflector toward the dish. |
proc.subreflectoracty1rate |
|
This parameter is the velocity of subreflector actuator Y1 in meters per second. The postion of the actuator at the beginning of a scan is given by the value of the parameter 'subreflectoract_y1'. Increasing Y actuator length moves the subreflector toward the dish. |
proc.subreflectoracty2 |
|
This parameter is the position of subreflector actuator Y2 in meters. Increasing Y actuator length moves the subreflector toward the dish. |
proc.subreflectoracty2rate |
|
This parameter is the velocity of subreflector actuator Y2 in meters per second. The postion of the actuator at the beginning of a scan is given by the value of the parameter 'subreflectoract_y2'. Increasing Y actuator length moves the subreflector toward the dish. |
proc.subreflectoracty3 |
|
This parameter is the position of subreflector actuator Y3 in meters. Increasing Y actuator length moves the subreflector toward the dish. |
proc.subreflectoracty3rate |
|
This parameter is the velocity of subreflector actuator Y3 in meters per second. The postion of the actuator at the beginning of a scan is given by the value of the parameter 'subreflectoract_y3'. Increasing Y actuator length moves the subreflector toward the dish. |
proc.subreflectoractx1 |
|
This parameter is the position of subreflector actuator X1 in meters. Increasing X actuator length moves the subreflector away from the feed arm. |
proc.subreflectoractx1rate |
|
This parameter is the velocity of subreflector actuator X1 in meters per second. The postion of the actuator at the beginning of a scan is given by the value of the parameter 'subreflectoract_x1'. Increasing X actuator length moves the subreflector away from the feed arm. |
proc.subreflectoractx2 |
|
This parameter is the position of subreflector actuator X2 in meters. Increasing X actuator length moves the subreflector away from the feed arm. |
proc.subreflectoractx2rate |
|
This parameter is the velocity of subreflector actuator X2 in meters per second. The postion of the actuator at the beginning of a scan is given by the value of the parameter 'subreflectoract_x2'. Increasing X actuator length moves the subreflector away from the feed arm. |
proc.subreflectoractz1 |
|
This parameter is the position of subreflector actuator Z1 in meters. Increasing Z actuator length moves the subreflector away from the feed arm elevator. |
proc.subreflectoractz1rate |
|
This parameter is the velocity of subreflector actuator Z1 in meters per second. The postion of the actuator at the beginning of a scan is given by the value of the parameter 'subreflectoract_z1'. Increasing Z actuator length moves the subreflector away from the feed arm elevator. |
proc.offsetfocus1x |
|
There is no help. yet, for offsetfocus1x |
proc.offsetfocus1xrate |
|
There is no help. yet, for offsetfocus1xrate |
proc.offsetfocus1y |
|
There is no help. yet, for offsetfocus1y |
proc.offsetfocus1yrate |
|
There is no help. yet, for offsetfocus1yrate |
proc.offsetfocus1z |
|
There is no help. yet, for offsetfocus1z |
proc.offsetfocus1zrate |
|
There is no help. yet, for offsetfocus1zrate |
proc.offsetfocus2x |
|
There is no help. yet, for offsetfocus2x |
proc.offsetfocus2xrate |
|
There is no help. yet, for offsetfocus2xrate |
proc.offsetfocus2y |
|
There is no help. yet, for offsetfocus2y |
proc.offsetfocus2yrate |
|
There is no help. yet, for offsetfocus2yrate |
proc.offsetfocus2z |
|
There is no help. yet, for offsetfocus2z |
proc.offsetfocus2zrate |
|
There is no help. yet, for offsetfocus2zrate |
proc.neworigin |
Off , "User set", Orbit , Sun , Moon , Mercury , Venus , Mars , Jupiter , Saturn , Uranus , Neptune , Pluto , UserTabl |
The New Origin parameter specifies a new location for the origin (longitude = latitude = 0) of the specified Coordinate Type. If a known object is selected or orbital elements are specified, the new origin will be computed automatically to track the center of that object. |
proc.originlongitude |
|
The Origin Longitude is the longitude offset of the new origin in the selected Coordinate Type when the New Origin is selected as to 'User set'. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originlongvel |
|
The Origin Longitude Velocity is the rate of change of the longitude offset of the new origin in the selected Coordinate Type when the New Origin is selected as to 'User set'. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originlatitude |
|
The Origin Latitude is the latitude offset of the new origin in the selected Coordinate Type when the New Origin is selected as to 'User set'. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originlatvel |
|
The Origin Latitude Velocity is the rate of change of the latitude offset of the new origin in the selected Coordinate Type when the New Origin is selected as to 'User set'. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originrotation |
|
The Origin Rotation is the rotation the new origin's equator with respect to the equator in selected Coordinate Type when the New Origin is selected as 'User set'. Positive rotation is counterclockwise as the observer sees it on the sky. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originrotvel |
|
The Origin Rotation Velocity is the rate of rotation of the new origin's equator with respect to the equator in selected Coordinate Type when the New Origin is selected as 'User set'. Positive rotation is counterclockwise as the observer sees it on the sky. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originstartutc |
|
The Origin Start Utc is the UTC for which the new origin longitude and latitude are valid when any of the rates, 'originlongvel', 'originlatvel', or 'originlatvel', is not zero. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.originstartlst |
|
The Origin Start Lst is the LST for which the new origin longitude and latitude are valid when any of the rates, 'originlongvel', 'originlatvel', or 'originlatvel', is not zero. The Origin Start LST is immediately converted to Origin Start UTC, which is the primary time system. The New Origin lets you specify the location of a temporay new origin for your coordinate grid so that the telescope beam position can specified with respect to the new origin. This origin may move at a specified rate in longitude and latitude, and the new equator may be rotated with respect to the parent Coordinate Type equator. The new origin is fully specified by the parameters 'originlongitude', 'originlongvel', 'originlatitude', 'originlatvel', 'originrotation', 'originrotvel', and 'originstartutc' or 'originstartlst'. The coordinate value units are degrees and degrees per second. |
proc.orbitrefframe |
" Earth B1950 ", " Earth J2000 ", "Sun/Ecliptic B1950", "Sun/Ecliptic J2000" |
The Orbit Reference Frame defines the inertial frame and spherical coordinate system in which the orbit is defined by the orbital parameters. The choices are EARTH_B1950, EARTH_J2000, ECLIPTIC_B1950, and ECLIPTIC_J2000. The first two are use equatorial coordinates for earth-orbiting satellites, and the others are used for solar system objects in ecliptic coordinates using either the B1950 or J2000 vernal equinox. |
proc.orbitepoch |
|
The Orbit Epoch is the fractional Modified Julian Date (MJD = JD - 2400000.5) for which the orbital elements are valid. In particular, if the Mean Anomaly is specified instead of Pericenter Epoch to define the position of the object in its orbit, this Mean Anomaly is at the the time of the Orbit Epoch. In that case the orbit epoch must be entered with enough precision to define the object's position accurately. |
proc.pericenterepoch |
|
The Pericenter Epoch is the time, in fractional Modified Julian Date (MJD = JD - 2400000.5) when the orbiting object passes pericenter. The position of the object in its orbit can alternatively be specified by its Mean Anomaly, which is its mean position, in degrees, at the time given by the Orbit Epoch. Calculations of the object's position as a function of time will use the most recently specified of these two parameters. |
proc.meananomaly |
|
The Mean Anomaly is the mean position of the object at the time specified by the Orbit Epoch. The mean position is the angular distance, in degrees, from pericenter of the object if it had a uniform angular velocity throughout its orbit. This is given by 360 multiplied by the time since pericenter passage divided by the orbit period. The position of the object in its orbit can alternatively be specified by its Pericenter Epoch. Calculations of the object's position as a function of time will use the most recently specified of these two parameters. |
proc.semimajoraxis |
|
The Semimajor Axis of the object's orbit is specified in kilometers. The size of the orbit may alternatively be specified by its Orbit Period or its Mean Daily Motion. These assume either the mass of the sun or mass of the earth, as implied from the selected Orbit Reference Frame, to derive the Semimajor Axis. The most recently specified of the three parameters will be used to compute the values of the other two. |
proc.orbitperiod |
|
The Orbital Period is specified in days. Alternatively, the object's Mean Daily Motion may be specified, where the Orbital Period = (360 / Mean Daily Motion). Specifying either of these two parameters will cause the Semimajor Axis to be computed with the assumption of the mass of the sun or mass of the earth, as implied from the selected Orbit Reference Frame. The most recently specified of the three parameters, Semimajor Axis, Orbital Period, or Mean Daily Motion, will be used to compute the values of the other two. |
proc.meandailymotion |
|
The Mean Daily Motion is the average angular velocity, in degrees per day, of the object in its orbit as computed from (360 degrees / Orbit Period in days). Alternatively, the object's Orbital Period may be specified. Specifying either of these two parameters will cause the Semimajor Axis to be computed with the assumption of the mass of the sun or mass of the earth, as implied from the selected Orbit Reference Frame. The most recently specified of the three parameters, Semimajor Axis, Orbital Period, or Mean Daily Motion, will be used to compute the values of the other two. |
proc.eccentricity |
|
Eccentricity of the orbit is pretty well self-evident. Alternatively, the Pericenter Distance may be specified. The most recently specified of the two parameters will be used to compute the value of the other using the current value of the Semimajor Axis. |
proc.pericenterdistance |
|
The Pericenter Distance is the distance, in kilometers, of the orbiting object from the central mass at closest approach. Alternatively, the orbital Eccentricity may be specified. The most recently specified of the two parameters will be used to compute the value of the other using the current value of the Semimajor Axis. |
proc.pericenterargument |
|
The Pericenter Argument is the angular distance, in degrees, from the ascending node to the pericenter in the plane of the orbit. |
proc.longascendingnode |
|
The Longitude of the Ascending Node is the angular distance, in degrees, from the vernal equinox to the point where the orbiting object passes through the reference plane (equator or ecliptic) from south to north. |
proc.orbitinclination |
|
The Orbit Inclination is angle, in degrees, between the orbital plane and the reference plane (equator or ecliptic). Its value is between 0 and 90 degrees. |
proc.parm1 |
|
This parameter, parm1, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm2 |
|
This parameter, parm2, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm3 |
|
This parameter, parm3, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm4 |
|
This parameter, parm4, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm5 |
|
This parameter, parm5, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm6 |
|
This parameter, parm6, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm7 |
|
This parameter, parm7, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm8 |
|
This parameter, parm8, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
proc.parm9 |
|
This parameter, parm9, is one of nine generic string value parameters that may be used in writing new procedures in glish. |
|
Antenna (ant)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| ant.nextscannumber |
|
The Next Scan Number allows you to reset the scan number to a new value for the next scan executed. |
ant.projid |
|
The Project ID is the number assigned to your program on the telescope schedule, e.g., B345. This string is used as a directory name for the antenna position data. |
ant.sourcename |
|
Any Source Name less than 32 characters. For the antenna the Source Name is only an identifier label that is saved with the antenna data during a scan. |
ant.scanid |
|
The Scan I.D. is a supplement to the Source Name for labeling the data. It has no effect on the data taking process. The string must be less than 32 characters. |
ant.scanlength |
|
The Scan Length is the duration of the scan in seconds. If the total time given by any of the antenna or focus position segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. |
ant.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
ant.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
ant.coordinatemode |
J2000 , B1950 , RaDecOfDate , ApparentRaDec, Galactic , HaDec , AzEl , Encoder |
The Coordinate Mode defines the coordinate system in which the direction of the telescope beam is specified. This coordinate system applies to the Primary Segment and Primary Offset parameters and the coordinate system into which the User Transform coordinates are rotated. The available Coodinate Modes are J2000, B1950, RaDecofDate, ApparentRaDec, Galactic, HaDec, and AzEl. |
ant.primarysegments |
|
Primary Segments specify the position of the telescope beam on the sky in the selected Coordinate Mode during a scan. Each segment consists of a position and first and second position time derivatives in each of two coordinates, e.g. RA and Dec, and a segment duration. Time is in seconds for the duration and the derivatives. There can be any number of segments, but only the first one is displayed here. One segment is usually enough for most observations, in which case the duration should be equal to the scan length. If the total time given by the Primary Segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. The time field displayed is the segment duration. |
ant.primefocussegments |
|
Prime Focus Segments specify the position of the prime focus receiver box in axial focus (meters), rotation or polarization (degrees), and translation (meters) in the GBT plane of symmetry orthogonal to the axial focus. If focustracking is 'On' or 'Fixed', the focus and translation segment values are with respect to the nominal position as determined by the built-in focus tracking algorithm. Each segment consists of a position and first and second position time derivatives in each of three coordinates, and a segment duration. Time is in seconds for the duration and the derivatives. There can be any number of segments, but only the first one is displayed here. Normally, the segments are specified by a glish routine, but you may enter and use one segment from this panel to position the prime focus box. If the total time given by the segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. The time field displayed is the segment duration. |
ant.offsetcoordinatemode |
J2000 , B1950 , RaDecOfDate , ApparentRaDec, Galactic , HaDec , AzEl , Encoder |
The Offset Coordinate Mode defines the coordinate system in which the direction of the telescope motion is specified. This coordinate system applies to the Primary Offset parameters. The available Offset Coodinate Modes are J2000, B1950, RaDecofDate, ApparentRaDec, Galactic, HaDec, and AzEl. |
ant.primaryoffsets |
|
Primary Offsets specify telescope beam position offsets during a scan from the positions given by the Primary Segments in the selected Coordinate Mode during a scan. Each segment consists of a position and first and second position time derivatives in each of two coordinates, e.g. RA and Dec, and a segment duration. Time is in seconds for the duration and the derivatives. There can be any number of segments, but only the first one is displayed here. Normally, the segments are specified by a glish routine. If the total time given antenna position segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. The time field displayed is the segment duration. |
ant.primaryunits |
Deg/Deg, Hrs/Deg, Rad/Rad |
The Primary Units parameter specifies the units used by the Primary Segments and Primary Offsets. The choices are Hrs/Deg, Deg/Deg, and Rad/Rad. Hrs/Deg normally only applies to RA/Dec and HA/Dec but can be applied to other coordinates. |
ant.usertransform |
|
The User Transform specifies a user-defined spherical coordinate system with a three-axis coordinate rotation from the selected coordinate system, e.g. J2000, AzEl, etc. The rotations may be made time dependent, for tracking solar system objects, by specifying first and second derivatives for each rotation component. Also, any number rotation segments may be concatenated, if one parabolic track is not sufficient. The coordinate rotation "track" is independent of scan times and durations, but the segments must span the time of any scans that use the UserDefined Coordinate Mode. The time fields refer to the MJD and UTC, in seconds, for the beginning of the segment. The three coordinate rotations are around the Z, X, and Z axes, in that order. The Z axis is through the positive pole (except for the left-handed AzEl system where it is through the nadir); the X axis is through longitude = latitude = 0; and the Y axis is through longitude = 90 degrees, latitude = 0. The rotations are specified in units determined by the 'primaryunits' parameter with time in seconds for the velocity and acceleration. |
ant.usertransformorder |
XYX, XYZ, XZX, XZY, YXY, YXZ, YZX, YZY, ZXY, ZXZ, ZYX, ZYZ |
The User Transform Order parameter allows the user to invoke any spherical coordinate rotation from a user defined system to the currently selected coordinate mode. The rotation axes are defined as a right-hand coordinate system, where Z is toward the current pole, and X is toward the zero point on the current equator. For example, you can define a new origin and equator orientation at a J2000 Ra/Dec point with an XYZ rotation order. The X rotation orients the new equator parallel to the J2000 equator, the Y rotation moves the new equator onto the J2000 equator, and the Z rotation moves the new equinox to the J2000 equinox. The rotation order choices are XYX, XYZ, XZX, XZY, YXY, YXZ, YZX, YZY, ZXY, ZXZ, ZYX, and ZYZ |
ant.usertransformenable |
Off, On |
User Transform Enable determines whether a coordinate rotation, as defined by the User Transform and User Trasnsform Order, is to be done in the selected Coordinate Mode spherical coordinates. This allows you to define a new coordinate origin and pole. For example, you could set the 'equinox' of our coordinates on an object to be mapped and rotate the 'equator' to align with the objects major axis. The user transform is employed to track a solar system object, but the parameters for keeping the origin on the object are computed automatically. To set up a new origin from the GUI panels, select 'User Transform' with the 'Other Panels' button in the Antenna Setup panel. The full user transform parameter is a glish record with as many segments as are required to track a moving object. To set a fixed origin redefinition use the New Origin parameters in the procedures group. |
ant.xyzsubreflectorsegments |
|
The Subreflector Segments specify the position, velocity, and acceleration of the subreflector in the XYZ directions during a scan. Positive X moves the subreflector away from the feed arm tower. Positive Y moves the subreflector away from the main reflector. Positive Z moves the subreflector toward the evevator side of the telescope. If focustrackingmode is On, these positions are with respect to the nominal best-focus position for the current elevation. Otherwise, the XYZ positions are with respect to best focus at the telescope rigging angle. The units are meters. There may be any number of segments, normally set by a glish routine, but only the first segment is displayed here. Each segment has a specified duration. If only one segment is used, its duration should be set equal to the scan length. If the total time given by the segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. |
ant.actsubreflectorsegments |
|
The Subreflector Segments specify the position, velocity, and acceleration of each subreflector actuator during a scan. The units are meters and seconds. As the actuator values increase their length increases. Generally, increasing Xn moves the subreflector away from the feadarm, increasing Yn moves the subreflector toward the main reflector, and increasing Z1 moves the subreflector away from the elevator side of the telescope. There may be any number of segments, normally set by a glish routine, but only the first segment is displayed here. Each segment has a specified duration. If only one segment is used, its duration should be set equal to the scan length. If the total time given by the segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. |
ant.subreflectorsegmenttype |
XYZ , Actuators, Offsets |
The Subreflector Segment Type specifies the axis type to which the Subreflector Segment position commands apply. The choices are to translate it in XYZ coordinates, command the six actuator positions directly, or specify F1 and F2 offsets. |
ant.f1offsets |
|
F1 Offsets specify the first focus position offsets during a scan. The units are meters and seconds. These offsets may be defined by any number of segments. Each segment contains a position and first and second position time derivatives for each axis plus a duration for the segment. Time for the duration and derivatives is in secods. If the total time given by the position segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. |
ant.f2offsets |
|
F2 Offsets specify the second focus position offsets during a scan. The units are meters and seconds. These offsets may be defined by any number of segments. Each segment contains a position and first and second position time derivatives for each axis plus a duration for the segment. Time for the duration and derivatives is in secods. If the total time given by the position segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. |
ant.pointingcorrections |
On , Off |
The Pointing Corrections parameter specifies the type of pointing model to which the Pointing Coefficients apply. This pointing model is for repeatable pointing errors that do not depend on temperature, wind, or other time-variable factors. The choices are ???? |
ant.azpointingcoefficients |
|
The Azimuth Pointing Coefficients describe the azimuth component of the repeatable telescope pointing error in the pointing model specified by the Pointing Mode parameter. |
ant.elpointingcoefficients |
|
The Elevation Pointing Coefficients describe the elevation component of the repeatable telescope pointing error in the pointing model specified by the Pointing Mode parameter. |
ant.pointingcoefficients |
|
The Pointing Coefficients describe the repeatable telescope pointing error in the pointing model specified by the Pointing Mode parameter. |
ant.localpointingoffsets |
|
The Local Pointing Offsets specify constant offsets to the telescope pointing. Az. 1 and Elev. are encoder offsets. Az. 2 is multiplied by secant(elev). |
ant.refractioncorrections |
On , Off |
Refraction Corrections enables or disables refraction corrections as specified by the Refraction Coefficients. The parameter value choices are On and Off. |
ant.obsfrequency |
|
The Observing Frequency parameter, in GHz, is used to determine ... |
ant.epoch |
|
This parameter is the epoch of the coordinateMode. Active only when coordinateMode is set to RaDecOfDate. Otherwise this value provides feedback. |
ant.cosminormode |
On , Off |
The Cosine Minor parameter controls whether position offsets in the major coordinate (RA, Azimuth, or Longitude) are multiplied by the secant of the minor coordinate (Dec, Elevation, or Latitude). The choices are On and Off. |
ant.surfacetolerance |
|
Surface Tolerance is used by the active surface system to determine the actuator update interval. |
ant.activesurface |
Off , " Open Loop ", "Closed Loop" |
The Active Surface parameter controls active surface tracking mode. The choices are Off, ... |
ant.focustracking |
On , Off |
The Focus Tracking parameter controls the application of focus tracking offsets to the subreflector position. |
ant.parallacticangletracking |
On , Off |
The Parallactic Angle Tracking parameter controls the tracking of the projected rotation of celestial objects at the telescope's focal plane as a function of azimuth and elevation. The choices are On and Off. |
ant.gregorianrcvr |
"1.2-1.7 GHz", "1.7-2.6 GHz", "4.0-5.8 GHz", " 8-10 GHz ", " 12-15 GHz ", " 18-22 GHz ", " 22-26 GHz ", " 26-40 GHz ", " 40-50 GHz ", " 68-95 GHz ", " 90-115 GHz" |
The Gregorian Receiver parameter determins which secondary focus receiver is rotated into to observing position with the receiver turret. The choices are
L_BAND (1.2-1.7 GHz)
S_BAND (1.7-2.6 GHz)
C_BAND (4.0-5.8 GHz)
X_BAND ( 8-10 GHz )
KU_BAND ( 12-15 GHz )
K_BAND_LOW ( 18-22 GHz )
K_BAND_HIGH ( 22-26 GHz )
KA_BAND ( 26-40 GHz )
Q_BAND ( 40-50 GHz )
W_BAND_LOW ( 68-95 GHz )
W_BAND_HIGH ( 90-115 GHz) |
ant.opticsmode |
Gregorian , "Prime Focus", Stow |
The Optics Mode parameter determines the optical geometry to be used. The choices are Gregorian, PrimeFocus, and Stow |
ant.weathersource |
"Weather Station", " Direct Entry " |
The Weather Source parameter determines the source of weather information, including ambient temperature, pressure, dew point, wind speed, and wind direction. The choices are Weather Station and User Input. When "User Input" is selected the Temperature, Pressure, Dew point, Wind speed, and Wind direction parameters must be specified by typing them into the entry boxes or from command line input. |
ant.ambienttemp |
|
Temperature is the outside air temperature, in degrees Celsius, used by the antenna controller for refraction corrections. When the "User Input" Weather Source is selected this field must be filled in the entry box. |
ant.ambientpressure |
|
Pressure is the air pressure, in millibars, used by the antenna controller for refraction corrections. When the "User Input" Weather Source is selected this field must be filled in the entry box. |
ant.ambienthumidity |
|
Dew point is the outside air dew point, in degrees Celsius, used by the antenna controller for refraction corrections. When the "User Input" Weather Source is selected this field must be filled in the entry box. |
ant.windspeed |
|
Wind Speed is in meters per second. When the "User Input" Weather Source is selected this field must be filled in the entry box. |
ant.winddirection |
|
Wind Direction is in degrees. When the "User Input" Weather Source is selected this field must be filled in the entry box. |
ant.stopaction |
AllStop , KeepTracking |
The Stop Action parameter controls the action of the telescope after a scan ends and before a new scan command is issued. The value 'allstop' causes the telescope drive motors to stop. The value 'keeptracking' tells the telescope control to continue on the last issued tracking trajectory. |
ant.azimuthwrap |
Auto, CCW , CW |
The Azimuth Wrap parameter controls which of the two possible azimuth cable wrap positions are used for a given telescope azimuth in the ranges where there are two possibilities. The default is 'Auto' which lets the telescope control software determine the best choice. The value 'CCW' keeps the telescope azimuth in the range -90 to +270 degrees, and the value 'CW' keeps it in the range +90 to +450 degrees. Zero degrees is north and +90 degrees is east. |
ant.elevationwrap |
Auto , "Over Top" |
The Elevation Wrap parameter controls which of the two possible telescop elevation positions are used near the zenith. The value 'Auto' keeps the elevation less than 90 degrees. The value 'Over the Top' uses the range 90 to 95 degrees, which requires an azimuth position 180 degrees from what it would be in the 'Auto' position for a given place on the sky. |
ant.trackingbeam |
1, 2, 3, 4, M12, M34, C, fubar |
The tracking_beam parameter determines which feed of the receiver is to track the source (i.e. be on-source) |
ant.beam |
|
The beam parameter determines which feed of the receiver is to track the source (i.e. be on-source) |
ant.beamnames |
|
The beam_names parameter provides a list of valid selections for the beam parameter. |
ant.receiver |
NoiseSource, "0.290 - 0.395", "0.385 - 0.520", "0.510 - 0.690", "0.680 - 0.920", "0.910 - 1.230", "1.15 - 1.73", "1.73 - 2.60", "3.95 - 5.85", "8.00 - 10.1", "12.0 - 15.4", "18.0 - 22.4", "22.0 - 26.5", "40.0 - 50.0" |
The Receiver parameter, in conjunction with the Observing Type, determines a lot of default settings the setup up the GBT system to use the selected receiver. Make this selection before setting parameters for specific devices. |
ant.beamazoffset |
|
The offset in arcseconds of the beam from the receiver box center in the direction perpendicular to the elevation. This term becomes the azimuth offset when corrected for the secant(elevation). |
ant.beameloffset |
|
The offset in arcseconds of the beam from the receiver box center in the elevation direction. |
ant.simulationmode |
Off, On |
The Simulation Mode parameter allows the user to switch that antenna controller to a mode where it accepts legal commands but does not send those commands to the antenna drives hardware. |
ant.operatingmode |
DoStop , DoScan , GetControl, ReleaseCtl, StowAzEl , UnStowAzEl, SelectFeed, CngOptics |
The Operating Mode parameter puts the antenna in one of a number of configurations for performing functions such as stowing the Az/El drives, rotating the receiver turret, or changing from Gregorian to prime focus operation. These functions are normally performed automatically so the observer usually doesn't set this parameter explicitly. The choices are:
DoStop - stops antenna tracking while in the ready state.
DoScan - This is the primary mode used for observing. In this mode, the antenna system will attempt to enable the necessary axes and move as specified by the appropriate segments parameters.
GetControl - A maintenance function, which attempts to acquire control from the servo systems.
ReleaseControl - The opposite of GetControl.
StowAzEl - This will command the antenna to stow its Az and El axes.
UnStowAzEl - Opposite of Stow
SelectFeed - This command will move the antenna elevation to 77.67 degrees to level the turret and then unlock, rotate, and relock the turret to move the receiver specified by the gregorianreceiver parameter into the operating position.
ChangeOptics - This command will move the primr focus receiver boom and subreflector to change the optical configuration of the telescope. There are three selections: PrimeFocus, Gregorian, and Stow. The first two are obvious, the third retracts the prime focus boom, and also moves the subreflector to its fully retracted position |
ant.driveenablemask |
|
The Drive Enable Mask is a low-level control boolean mask for enabling the various antenna drive systems. The observer will not normally set these directly. To the antenna controller the mask is a glish record of the form [az=T, el=T, pffocus=T, pfpolar=T, pfx=T, Y1=F, Y2=F, Y3=F, X1=F, X2=F, Z1=F], where the first two members are for the Az/El drives, the next three for the prime focus box drive, and the last six for the subreflector actuators. This mask may be set from the GBT Observe table with a dot delimited boolean string, e.g., 'T.T.T.T.T.F.F.F.F.F.F'. A value of T means that the brakes are released and the servo loop is closed. |
ant.polarmotioncorrection |
On , Off |
The Polar Motion Correction parameter controls whether this correction to pointing is applied or not. |
ant.diurnalaberrationcorrection |
On , Off |
The Diurnal Aberration parameter controls whether this correction to pointing is applied or not. |
ant.scannumber |
|
The Scan Number normally updates at the beginning of each scan, but it may be reset by specifying a new value for nextscannumber. The Scan Number itself is read only. |
|
Spectral Processor (sp)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| sp.nextscannumber |
|
The Next Scan Number allows you to reset the scan number to a new value for the next scan executed. |
sp.projid |
|
The Project ID is the number assigned to your program on the telescope schedule, e.g., B345. This string is used as a directory name for your data. |
sp.sourcename |
|
Any Source Name less than 32 characters. In pulsar observing this name is used to fetch the current pulsar timing parameters and must be in a standard 'hhmmsdd' format, e.g., 0329+54. In other observing modes the Source Name is only an identifier label. |
sp.scanid |
|
The Scan I.D. is a supplement to the Source Name for labeling the data. It has no effect on the data taking process. The string must be less than 32 characters. |
sp.scanlength |
|
The Scan Length is the duration of the scan in seconds. Any data integrations completed after the end of a scan will normally be discarded. Hence, the Scan Length is typically an integer number of integration times plus a second or two. |
sp.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
sp.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
sp.processormode |
DedispTimeSamples, StdSpectLine, SyncFreqTime |
The Processor parameter selects from the predefined spectral processor configurations. The GBT User interface currently recognizes modes 1 (DedispTimeSamples), 7 (StdSpectLine), and 10 (SyncFreqTime). |
sp.switchmode |
"Total Pwr", "Freq Sw ", "User Def." |
The Switching Mode parameter selects from a number of predefined spectral line switching configurations for the spectral processor. The 'User Defined' mode must be defined with the Spectral Processor subpanel. |
sp.configuration |
"2x1024 IFxCh", "4x512 IFxCh", "4x256 IFxCh", "8x256 IFxCh" |
The spectral processor Configuration selects from the four available combinations of number of IF's and number of spectral channels per IF |
sp.bandwidth |
" 40 MHz ", " 20 MHz ", " 10 MHz ", " 5 MHz ", "2.5 MHz ", "1.25 MHz ", "0.625 MHz", "0.312 MHz", "0.156 MHz", "0.078 MHz" |
The Bandwidth parameter selects from ten available bandwidths per IF channel from 40 MHz down to 78 kHz. The bandwidth upper limit is 20 MHz for Configurations of 4 IF's and 10 MHz for the 8-IF Configuration |
sp.integrationtime |
|
This parameter is the Integration Time for one data record written to disk. Partial integrations at the end of a scan are normally discarded so you will want the Scan Length to be an integer number of Integration Times plus a second or two to be sure that the last integration is completed. Long integrations risk greater loss of data from a corrupted integration while shorter integrations fill up the disk faster. |
sp.atodlevelmode |
Immediate , "Scan Start" |
The A/D Leveling Mode determines when the attenuator settings are changed. The ScanStart selection causes the attenuators to be set just before each scan starts, if the Balance selection is 'yes' |
sp.balance |
Yes, No |
Balance specifies whether or not the input levels to the A/D convertors are set at the beginning of a scan (or immediately if selected by the A/D Level Mode). |
sp.multipliermode |
Square , Cross , SqrCross |
Multiplier Mode sets the configuration of the multiplier following the output of each complex FFT and real correction. The three possibilities are to square the output spectral values, cross multiply the outputs from racks A and B for polarization or other cross-correlation work, or do both if the bandwidth permits the multiplier to run twice as fast as the FFT engine. |
sp.taper |
Box , Cosine , Halfbox |
The Taper specifies the weighting function to be applied to the input A/D amplitude-vs-time series before it is transformed. In spectral processor hardware memos the taper function is called a window. The Box taper weights all input samples equally, Cosine uses a half-cosine cycle as a weighting function, and Halfbox uses unity weight in the center half of the samples and zero for the first and last quarter (mainly for test purposes). The taper affects the spectrometer resolution, spectral channel 'sidelobes', and, to some extent, the spectrometer sensitivity. |
sp.caldutycycle |
|
Cal Duty Cycle specifies the duration of the pulsed calibration signal. In the pulsar timing mode this is the fraction of the pulsar period. In dedispersion mode the cal fires at a one-second interval, and the Cal Duty Cycle is the fraction of this interval. The value must be between 0.0 and 1.0. This parameter is ignored in other modes. It is used in conjuction with Cal Phase |
sp.calphase |
|
Cal Phase specifies the start time of the calibration pulse. In the pulsar timing mode, Cal Phase specifies the start phase with respect to the beginning the pulse window in fraction of a pulse period. In dedispersion mode the cal fires at a one-second interval, and the Cal Phase is the fraction of this interval with respect to the start of the scan. The value must be between 0.0 and 1.0. This parameter is ignored in other modes. It is used in conjuction with Cal Duty Cycle. |
sp.dispersionmeasure |
|
Dispersion Measure is used for computing start time offsets in pulsar-synchronous spectral processor modes so that the pulse is placed in the data location specified by Pulse Offset. This parameter is also used in pulsar dedispersion modes to configure the accumulator map. The unit is parsecs/cm**3. When a standard format Pulsar Name in entered the dispersion measure value will be picked up from the polyco.dat file. |
sp.pulseparam |
|
pulseParam is used for returning the actual pulsar dispersion measured used in the Spectral Processor. The unit is parsecs/cm**3. This values is usually obtained from the polyco.dat file. |
sp.polycodatfile |
|
The Pulse Coefficients File is the name of the file that contains pulse frequency (1/period) coefficients for the pulsars to be observed. This file must be prepared before an observing run using the 'tempo' program. The output of 'tempo' is an ascii file, called polyco.dat, which may be used directly or converted to a binary file with the 'polybinary' program for faster execution at the beginning of each scan. File names with the .bin suffix are assumed to be binary. Files with all other suffixes are assumed to be ascii. |
sp.pulseperiod |
|
The Pulse Period is the period of the observed pulsar used to synchronously average the data over many pulse periods. This value is usually determined from the pulse frequency coefficients in the polyco file, as specified by the Pulsar Name, plus a doppler correction. The pulse period may be specified directly, but it will not be updated for changing doppler shift during a scan as it is when taken from the coefficients file. |
sp.pulseoffset |
|
Pulse Offset specifies the offset of a pulse from the center of the pulse period window in a pulsar-synchronous accumulation mode. The offset is in fraction of a pulse period between -1.0 and 1.0. To the accuracy of the predicted pulse arrival time from the polyco file, the scan start time is adjusted to place the pulse in the selected accumulation window phase. In many cases the pulse phase has drifted since the last update of the data used in the polyco calculation so an initial observation may be required to get the current pulse offset. |
sp.sampletime |
|
Sample Time is the accumulation time, in seconds, for each time bin in the continuous dedispersion mode of the spectral processor. This time will be adjusted to an integer number of FFT cycle times |
sp.numberofphases |
|
The Number of Phases specifies how many phases are in the switching cycle. This number is predetermined by the selected Switching Mode for all but the "User Defined" mode. In that mode the number may be between 2 and 16. |
sp.phasestart |
|
Each phase Start entry field specifies the beginning of this phase as a fraction of the total switch period. The first start time must be zero, they must increase monotonically, and the last phase start time must be less than one. The effective integration time for a phase in one switching cycle is the product of the Switch Period and the difference between that phase's and the next phase's start times minus the Blanking Time. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the phase Start times are predetermined by the selected switching mode. This parameter applies only to spectral line modes of the spectral processor |
sp.blankingtime |
|
Blanking Time is the time in seconds at the beginning of each switch phase when data integration is inhibited. The Blanking Time may be set to a different value for each phase through the glish command line, but one value is usually sufficient for every phase, and that value is specified here. The blanking time must be an integer number of FFT cycles, and the nearest possible value will be used. This parameter is used only in spectral line modes. |
sp.calstate |
On , Off |
In spectral line mode, each Cal toggle button specifies the state of the receiver calibration signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the Cal states are predetermined by the selected mode. |
sp.calpulsarstate |
On , Off |
In pulsar timing and dedispersion modes, this button simply specifies whether the calibration signal should be pulsed with the Cal Duty Cycle and Cal Phase specified. |
sp.sigrefstate |
Sig, Ref |
Each SigRef toggle button specifies the state of the receiver frequency/load/beam switch signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the SigRef states are predetermined by the selected mode. |
sp.switchperiod |
|
Switch Period is the period, in seconds, of the cal and sig/ref switching cycle. Since this period must be an integer number of FFT cycle times, the actual switch period will be adjusted to the nearest possible value. |
sp.fftsperbin |
|
FFT's/Bin is for information only since it is set automatically. It is the number of FFT's in each time bin in the pulsar timing spectral processor mode. |
sp.actualtimebins |
|
This parameter shows the Actual Number of Time Bins in a pulse period after computing the optimum master clock frequency and the closest number of time bins to the request number. This is a read-only parameter. |
sp.addpolarizations |
Yes, No |
The Add Polarization flag turns on a requested software patch in the pulsar timing mode of the spectral processor to add spectra from two polarizations together in the hardware accumulator. This reduces the data rate into observer-supplied data acquisition equipment. It assumes that one polarization is hooked to IF A1 (B1) and the other to A2 (B2). |
sp.bypassstage |
Yes, No |
Bypass Stage sets the status of each board in the spectral processor rack to either normal or bypass for hardware diagnostic purposes. This parameter is spring loaded in the sense that all boards will be reset to Normal after the end of a scan to prevent accidentally leaving a board bypassed during observing. The board number designations are:
m = 1: window board
m = 2-12: FFT stages 0-10
m = 13-14: real corrector stages
m = 15: square/cross real
m = 16: square/cross imaginary
m = 17: square/cross switched |
sp.clockfrequency |
|
The spectral processor master Clock Frequency is for information only. In pulsar modes it is computed from the pulsar period, number of time bins, etc. Its allowable range is 150 to 160.3 MHz. In spectral line mode the clock is fixed at 160 MHz. |
sp.datashift |
2, 3, 4, 5 |
Data Shift determines the bit range of the conversion of 32-bit data from the FFT engine to 16-bit data into the square/cross multiplier stage. In special cases where FFT output noise quantization might be a problem, such as low IF input levels, the data word shift may be increased. The default value is 2 bits, which means that the highest 2 bits (sign-extended) are dropped from the FFT output word. Since the FFT output is in the voltage domain, 2 bits is equivalent to the highest 4 bits in the power product. Available values for data shift are 2, 3, 4, and 5. The higher values produce larger power spectrum output values for a given FFT input level. |
sp.deadfftstagea |
|
Dead FFT Stage is a list of statuses of 11 hardware FFT stages. If a stage is dead, it may be flagged here so that it is switched out of the system. There is one completely spare stage. The numbers of stages required in the various configurations are
2 IF x 1024 ch: 10 (1 spare)
4 IF x 512 ch: 9 (2 spares)
4 IF x 256 ch: 8 (3 spares)
8 IF x 256 ch: 8 (3 spares) |
sp.deadfftstageb |
|
Dead FFT Stage is a list of statuses of 11 hardware FFT stages. If a stage is dead, it may be flagged here so that it is switched out of the system. There is one completely spare stage. The numbers of stages required in the various configurations are
2 IF x 1024 ch: 10 (1 spare)
4 IF x 512 ch: 9 (2 spares)
4 IF x 256 ch: 8 (3 spares)
8 IF x 256 ch: 8 (3 spares) |
sp.fastformat |
Yes, No |
The Fast Format flag controls whether 32-bit or 16-bit words are transferred out of the accumulator. The 16-bit words are the least significant accumulator bytes so this word size is useful only for short integrations where the word does not overflow. This option has been used mainly with high speed dedispersed data streams, particularly in connection with the Raw Data parameter, but it works in other modes. |
sp.randomoffset |
Yes, No |
In pulsar spectral processor modes the start time is advanced by a randomly generated time equal to a fraction of one time bin to reduce any timing bias due to time bin quantization. This offset may be turned off with the Random Offset flag. |
sp.rawdata |
Off , B1 , B2 , B3 , B4 , W1 , W2 , W3 , Full |
The Raw Data selection is used to bypass data formatting so that accumulator data is transferred directly to disk with a minimum of processing. This option was added mainly for high speed sampling in the pulsar dedispersion mode, but it works in other modes. In the dedispersion mode the value of RD may be set to select any 8, 16, or 32-bit portion of the samples from the accumulator. The choices are
Off Raw data turned off (default)
B1 Save only the least significant byte.
B2 Save only the second least significant byte.
B3 Save only the third least significant byte.
B4 Save only the most significant byte.
W1 Save the least significant 16-bit word, bytes 1&2
W2 Save the middle 16-bit word, bytes 2&3
W3 Save the most significant 16-bit word, bytes 3&4
Full Save the full accumulator 16 or 32 bit word as
set by the Fast Format parameter.Values B3, B4, W2, and W3 work only when the full 32-bit word is transferred from the accumulator (Fast Format off). Only Raw Data selections 'Off' and 'Full' work in the non-dedispersion modes. |
sp.rackstatus |
Off , "Rack A", "Rack B", Both |
The spectral processor is actually two independent FFT engines which, in principle, may be run independently. Since this independence has never been used for observing, it is not provided for in this observer interface, except for Taper Offset. If glish commands are used to decouple the two FFT engines (racks), this status will be shown in the Rack Status field. The possibilities are both racks off, rack A only, rack B only, and both racks on (may or may not be being used independently). |
sp.taperoffset |
Yes, No |
The spectral processor is actually two separate FFT engines which, in principle, may be run independently. The Taper Offset flag selects whether the data sampling for the time series to be transformed in racks A and B are started together or are offset by half of a series length. If both racks look at the same IF signal, the offset provides inhanced sensitivity when spectra from the same IF are added together. The penalty is that there are half as many spectral channels to spread around the frequency dimensions. This option cannot be used in the 'Cross' or 'Square/Cross' Multiplier Mode since the inputs to racks A and B must be sampled synchronously. |
sp.testmode |
On , Off |
Test Mode controls whether spectral processor accumulator output data are sent to the FITS formatter in normal observing or directly to disk as raw data for comparison with known test results or with data from the other rack. This is a spring-loaded parameter in the sense that it returns to 'No', i.e. normal operation, after the completion of one scan. |
sp.testseed |
|
Test Seed is the integer seed value for the pseudo-random noise generator which is used as a test source for the spectral processor when the Test Source is set to 'Pseudo Short' or 'Pseudo Long'. If the Test Source is 'Fixed', Test Seed is the value of the constant input word. |
sp.testsource |
"A/D Output ", "Pseudo Short", "Pseudo Long ", "Fixed Value " |
Test Source selects the data source to the spectral processor input buffers. This is used only for test purposes, only. It is a spring-loaded parameter in the sense that it returns to normal input after the completion of one scan. The selections are 'A/D Output' for normal input from the A/D convertors, 'Pseudo Long' for pseudo-random noise with a very long repetition period, 'Pseudo Short' for pseudo-random noise with a short repetition period, and 'Fixed' for a constant input value. The value of the Test Seed parameter is used a the seed to the two pseudo-random noise generators or as the fixed input value |
sp.testfilename |
|
Test File Name is the name of the file where accumulator output is written in test mode. These data are compared with known test results or with data from the other spectral processor rack as a check on hardware operation. |
sp.atodinputlevel |
|
A/D Input Level sets the noise level at the input to each A/D convertor. The unit is the number of quantization intervals per noise rms level, normally between about 1.0 and 4.0. Lower numbers give more large signal handling room in the A/D but compromize sensitivity and baseline stability because of quantization effects. The IF attenuators will be set to produce an input level within about 0.7 dB of the one specified |
sp.caltemperature |
|
Cal Temperature is the calibration source intensity in Kelvins. This parameter has no direct effect on the operation of the spectral processor. Its value is passed on to the data header for later data reduction. |
sp.iffrequency |
|
The I.F. Frequencies are the center frequencies of IF passbands. After taking into account the baseband offset and other conversions in the IF drawer, these parameters set the frequencies of the synthesizers in the IF drawers or the frequency of the high resolution synthesizer if an external IF LO is selected. The actual passband center frequency may be slighly different from the values specified because the resolution of the internal synthesizers is 10 kHz. The actual IF center frequencies are recorded with the data. The center IF frequency corresponds to the center of channel N/2+1, where N is the number of channels in the spectrum, and the first channel number is 1. |
sp.ifsideband |
Upper, Lower |
IF Sideband selects the active single-sideband convertor sideband. With upper sideband, increasing frequency at the IF corresponds to increasing frequency at baseband. Lower sideband, produces decreasing frequency at baseband with increasing frequency in the IF passband. The RF Sideband parameter, as well as this parameter, affects the frequency transformation from sky to baseband frequency. In the final spectrum increasing channel number corresponds to increasing baseband frequency. |
sp.rfsideband |
Upper, Lower |
The RF Sideband specifies the sky-to-IF-passband frequency inversion for each IF channel. This is required in the hardware dedispersion modes, along with the IF Sideband, to determine the direction of dispersion. In other modes, these parameters are used to interpret the frequency direction of the output spectra. |
sp.skyfrequency |
|
The Sky Frequency specifies the center of the passband being observed. This parameter is required in the hardware dedispersion modes to convert dispersion measure into a time delay. In other modes, it is used to interpret the frequency scale of the output spectra. |
sp.cliplevel |
|
Clipping Level sets the maximum level that can be instantaneously applied to the input of the slow baseline integrator in the RFI detector. This clipping prevents severe over-charging and, hence, slow recovery of this integrator. This parameter is specified in volts applied to the clipper diode. The maximum values is 10 volts, which is the default. |
sp.excise |
Yes, No |
Excise turns real-time RFI excision on or off. RFI excision is based on total power threshold detection in each IF channel with the detector parameters being Threshold, Clip Level, and Fast and Slow Time Constants. |
sp.fasttimeconst |
1us , 3us , 10us , 30us , 100us, 300us, 1ms , 3ms , 10ms |
Fast Time Constant specifies the response time of the total power RFI threshold detector. The optimum value depends on the nature of the RFI but is usually roughly equal to the characteristic pulse length of the interference. |
sp.slowtimeconst |
100us, 300us, 1ms , 3ms , 10ms , 30ms , 100ms, 300ms, 1s |
Slow Time Constant sets the response time of the baseline comparison level for the total power RFI threshold detector. The optimum value depends on the nature of the RFI and is usually more than 10 times the characteristic time scale of the transient interference. RFI detection occurs when the fast-time-constant detector output exceeds the slow-time-constant output by the threshold value. |
sp.threshold |
|
Threshold specifies the level difference between the outputs of the fast and slow integrators that will flag an RFI transient. This value is specified in units of volts. The maximum value is 10 V. The optimum value must be set experimentally since it depends on the Bandwidth, A/D Input Level, Fast Time Constant, and interference characteristics. |
sp.iflosource |
Int, Ext |
The IF LO Source flag controls whether an IF drawer has its input center frequency set by its internal synthesizer with 10 kHz resolution or by the external synthesizer with 10 Hz resolution. There is only one external synthesizer that must be shared between IF drawer so the normat operation is with internal LO's. The external synthesizer is same one used for the spectral processor variable master clock, so it is not available in pulsar modes. |
sp.scannumber |
|
The Scan Number normally updates at the beginning of each scan, but it may be reset by specifying a new value for nextscannumber. The Scan Number itself is read only. |
|
Spectral Processor Storage (sp_stor)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| sp_stor.tapeid |
|
Tape ID is a four-digit tape identification number found on the tape cartridge. |
sp_stor.tapedirect |
No , Yes |
Tape Direct determines whether data are written directly to tape, instead of to disk. |
sp_stor.tapecontrol |
|
Tape Control tells whether a tape is in use. It has a value of -1 when no tape is in use. Otherwise it is equal to the Tape ID number. This is a read-only value. |
sp_stor.eoftrigger |
" No EOF ", "Scan End", Delayed |
EOF Trigger specifies whether file marks are written to tape at scan change or after pauses of a length set by EOF Delay. |
sp_stor.eofdelay |
|
If EOF Trigger is set to write after a pause in tape writing, EOF Delay sets this pause length in seconds. |
sp_stor.eofcontrol |
|
EOF Control tells whether an end-of-file will be written to tape. -1 = no EOF, 0 = at a new scan, otherwise the value is equal to EOF Delay. This parameter is read-only. |
sp_stor.writefile |
" All Data ", " No Data ", "Sample Only" |
Write File determines whether all data, no data, or only samples of data are written to disk or tape. Sample Interval sets the number of data records between writes, if this option is selected. |
sp_stor.filecontrol |
|
File Control tells whether a data record will be written. 0 = no writes, otherwise a record will be written when (record# % fileControl == 0). |
sp_stor.sampleinterval |
|
Sample Interval is the number of records between data writes when the Write File parameter is set to 'Sample'. |
sp_stor.filename |
|
File Name is the name of the file to which data are being written. This is determined automatically as a combination of time, date, and device ID. |
sp_stor.collate |
Yes, No |
Collate controls whether data from spectral processor racks A and B are collated into one data record before being written to disk or tape. |
sp_stor.log |
Yes, No |
Log controls whether a log of all data records is generated. |
sp_stor.flushbuffer |
|
Flush Buffer causes unwritten records to be written to disk or tape. This is normally used only when there is a problem with the data flow such as data interruption from one of the spectral processor racks when collation is turned on. |
|
Spectrometer (spm)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| spm.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the time mode with the menu button. In a.s.a.p. mode the time display is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. |
spm.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
spm.scanlength |
|
|
spm.nextscannumber |
|
|
spm.scannumber |
|
|
spm.projectid |
|
|
spm.sourcename |
|
|
spm.scanid |
|
|
spm.configuration |
Testing, A1, "A1 B1", "A1 B1 C1", "A1 B1 C1 D1", "A1 B1 C2", A2, "A2 B1", "A2 B1 C1", "A2 B2", A4, Pulsar |
Selects the base operational mode and and quadrant assignments of the GBT Spectrometer. |
spm.fastsamplers |
banka, bankb, bankc, bankd, notused |
The 1.6 GHz samplers are individually assigned to specific banks. |
spm.slowsamplers |
banka, bankb, bankc, bankd, notused |
The 100 MHz samplers are assigned to specific banks in groups of 8. |
spm.slowsamplerslevel |
3, 9 |
Selects 3-level or 9-level operation for each bank when using the slow samplers. |
spm.numberslowsamplers |
1, 2, 4, 8 |
The Number of slow samplers used for each bank of the spectrometer. Valid selections are 1, 2, 4, or 8. |
spm.relativebandwidth |
narrow, wide |
1.6 GHz samplers: 200 vs. 800 MHz bandwidth; or 100 MHz samplers:12.5 vs. 50 MHz bandwidth. |
spm.samplermode |
Fast, Slow |
Selects display of Fast or Slow sampler information. |
spm.correlations |
auto, cross |
Selects auto-correlation or cross-correlation. of signals |
spm.levels |
3, 9 |
Selects 3-level or 9-level A/D sampling. |
spm.numberofifs |
1, 2, 4, 8, 16, 32 |
Selects the desired total number of IFs (IF frequencies times number of polarizations) for the GBT Spectrometer setup. |
spm.bandwidth |
800MHz, 200MHz, 50MHz, 12.5MHz |
Selects the desired bandwidth for the GBT Spectrometer setup. |
spm.polarization |
Auto, Cross |
Produce polarization cross products. |
spm.calstate |
Off, On |
Each Cal toggle button specifies the state of the receiver calibration signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the Cal states are predetermined by the selected mode. |
spm.actualcalstate |
Off, On |
Each Actual Cal button specifies the actual state of the receiver calibration signal in the button's switching phase used in the spectrometer. |
spm.sigrefstate |
Sig, Ref |
Each SigRef toggle button specifies the state of the receiver frequency/load/beam switch signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the SigRef states are predetermined by the selected mode. |
spm.actualsigrefstate |
Sig, Ref |
Each SigRef toggle button specifies the actual state of the receiver frequency/load/beam switch signal in the button's switching phaseused within the spectrometer. |
spm.requestedintegrationtime |
|
Controls the approximate time in seconds (within 2 microseconds) of one data record. |
spm.blankingtime |
|
Banking Time is the time in seconds at the beginning of each switch phase when data integration is inhibited. The Blanking Time may be set to a different value for each phase through the glish command line, but one value is usually sufficient for every phase, and that value is specified here. The resolution in 100nS. |
spm.actualblanking |
|
Actual Banking Time is the time in seconds at the beginning of each switch phase when data integration is inhibited that was used in thespectrometer. |
spm.numberofphases |
|
The Number of Phases specifies how many phases are in the switching cycle. This number is predetermined by the selected Switching Mode for all but the "User Defined" mode. In that mode the number may be between 1 and 64. |
spm.actualnumberphases |
|
The Actual Number of Phases specifies how many phases are in the switching cycle used in the spectrometer. This number is predetermined by the selected Switching Mode for all but the "User Defined" mode. In that mode the number may be between 1 and 64. |
spm.switchperiod |
|
The Switch Period specifies the time in seconds of a full switch cycle. The Integration Time must be an integer number of Switch Periods and will be changed to the nearest value when a new Switch Period is entered. |
spm.phasestart |
|
Each Phase Start entry field specifies the beginning of this phase as a fraction of the total switch cycle. The first start time must be zero, they must increase monotonically, and the last phase start time must be less than one. The effective integration time for a phase in one switching cycle is the product of the Switch Period and the difference between that phase's and the next phase's start times minus the Blanking Time. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the phase Start times are predetermined by the selected mode. |
spm.actualphasestart |
|
Each Actual Phase Start entry field specifies the beginning of this phase as a fraction of the total switch cycle used in the spectrometer. |
spm.bankasss |
On , Off |
Selects up to six active switching signals for Bank A of the spectrometer. |
spm.bankbsss |
On , Off |
Selects up to six active switching signals for Bank B of the spectrometer. |
spm.bankcsss |
On , Off |
Selects up to six active switching signals for Bank C of the spectrometer. |
spm.bankdsss |
On , Off |
Selects up to six active switching signals for Bank D of the spectrometer. |
spm.switchingsignalsselect |
On , Off |
Selcts up to six active switching signals for each bank. |
spm.switchingsignalsmaster |
SpectralProcessor, DCR, Spectrometer |
The Switching Signals Master selects which backend provides the switching signals to all of the backends. |
spm.actualswitchperiod |
|
The Actual Switch Period specifies the time in seconds of a full switch cycle being used in the spectrometer. |
spm.balance |
Off, On |
Turns the balancing of the input to the samplers On or Off |
spm.balancemode |
ScanStart, Immediate |
Controls whether balancing is done upon activation or prior to a scan |
spm.state |
|
|
spm.status |
|
|
|
Convertor Rack (conv)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| conv.nextscannumber |
|
The Next Scan Number allows you to reset the scan number to a new value for the next scan executed. |
conv.projid |
|
The Project ID is the number assigned to your program on the telescope schedule, e.g., B345. This string is used as a directory name for your data. |
conv.sourcename |
|
Any Source Name less than 32 characters. In pulsar observing this name is used to fetch the current pulsar timing parameters and must be in a standard 'hhmmsdd' format, e.g., 0329+54. In other observing modes the Source Name is only an identifier label. |
conv.scanid |
|
The Scan I.D. is a supplement to the Source Name for labeling the data. It has no effect on the data taking process. The string must be less than 32 characters. |
conv.scanlength |
|
The Scan Length is the duration of the scan in seconds. Any data integrations completed after the end of a scan will normally be discarded. Hence, the Scan Length is typically an integer number of integration times plus a second or two. |
conv.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
conv.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
conv.abselect |
A, B |
The ConverterRack bank select switch (selects between Rack A and B's ConverterModules for the SpectralProcessor) |
conv.moduleactive |
|
The Module Active parameter sets which of the 16 converter modules in the Converter Rack are under control of the Converter Rack manager. |
conv.loactive |
Off, On |
The LO Active parameter sets which of the 8 frequency synthesizers (LO2) in the Converter Rack are under control of the Converter Rack manager. |
conv.inputselect |
A, B |
The Converter Input parameter selects between A and B inputs of each IF channel in the Converter Rack. These inputs are normally connected outputs of the optical fiber receiver modules. |
conv.outputselect |
1, 2, 3, 4 |
The Output Select parameter selects one of four output frequency ranges from each of the 16 IF channels in the Converter Rack. Selection 1 corresponds to the 150-2000 MHz output connector J3 (Sampler Filter); selection 2 to the 500-1000 MHz output connector J4 (VLBA DAR); selection 3 to four 150-550 MHz parallel outputs J5 (spectral processor), J6 (Converter Filter), J7 (spare), and J8 (spare); and selection 4 to the 150-2000 MHz output J9 (spare). |
conv.attenuator |
|
The Attenuator parameter sets the attenuator values for each of the 16 IF channels in the Converter Rack. The attenuator values can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator1 |
|
The Attenuator1 parameter sets the attenuator values for the 1st IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator2 |
|
The Attenuator2 parameter sets the attenuator values for the 2nd IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator3 |
|
The Attenuator3 parameter sets the attenuator values for the 3rd IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator4 |
|
The Attenuator4 parameter sets the attenuator values for the 4th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator5 |
|
The Attenuator5 parameter sets the attenuator values for the 5th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator6 |
|
The Attenuator6 parameter sets the attenuator values for the 6th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator7 |
|
The Attenuator7 parameter sets the attenuator values for the 7th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator8 |
|
The Attenuator8 parameter sets the attenuator values for the 8th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator9 |
|
The Attenuator9 parameter sets the attenuator values for the 9th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator10 |
|
The Attenuator10 parameter sets the attenuator values for the 10th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator11 |
|
The Attenuator11 parameter sets the attenuator values for the 11th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator12 |
|
The Attenuator12 parameter sets the attenuator values for the 12th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator13 |
|
The Attenuator13 parameter sets the attenuator values for the 13th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator14 |
|
The Attenuator14 parameter sets the attenuator values for the 14th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator15 |
|
The Attenuator15 parameter sets the attenuator values for the 15th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.attenuator16 |
|
The Attenuator16 parameter sets the attenuator values for the 16th IF channel in the Converter Rack. The attenuator value can be between 0 and 31.875 dB in 1/8th dB steps. Values are specified in floating point and the nearest available value is set. When the Converter Rack is used in connection with the autocorrelation GBT spectrometer these values may be set automatically by the sampler level balancing routine. |
conv.lofrequency |
|
The LO Frequency sets the frequency of each of 8 LO synthesizers in the Converter Rack. The output of each synthesiser is shared by two IF channels in this rack (often connected to two orthogonally polarized front-end channels to be observed at the same frequency). This is the second LO (LO2) in the GBT frequency conversion chain. Its range is 10500 to 18000 MHz, and it is used to conver frequencies in the 1 to 8 GHz passband of the optical fiber transceivers to a fixed second IF passband of 8500 to 10350 MHz. |
conv.lolevel |
|
The LO Level parameter sets the power level, in dBm, for each of the 8 frequency synthesizers (LO2) in the Converter Rack. |
conv.defaultsamplerate |
mr100MS, mr200MS, mr500MS, mr1Sec, mr2Sec, mr5Sec, mr10Sec, mr30Sec, mr1Min, mr2Min, mr5Min, mr10Min, mr30Min, mr1Hr |
Sets the rate at which the sampler is run. |
conv.scannumber |
|
The Scan Number normally updates at the beginning of each scan, but it may be reset by specifying a new value for nextscannumber. The Scan Number itself is read only. |
|
Digital Continuum Receiver (dcr)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| dcr.nextscannumber |
|
The Next Scan Number allows you to reset the scan number to a new value for the next scan executed. |
dcr.projid |
|
The Project ID is the number assigned to your program on the telescope schedule, e.g., B345. This string is used as a directory name for your data. |
dcr.sourcename |
|
Any Source Name less than 32 characters. In pulsar observing this name is used to fetch the current pulsar timing parameters and must be in a standard 'hhmmsdd' format, e.g., 0329+54. In other observing modes the Source Name is only an identifier label. |
dcr.scanid |
|
The Scan I.D. is a supplement to the Source Name for labeling the data. It has no effect on the data taking process. The string must be less than 32 characters. |
dcr.scanlength |
|
The Scan Length is the duration of the scan in seconds. Any data integrations completed after the end of a scan will normally be discarded. Hence, the Scan Length is typically an integer number of integration times plus a second or two. |
dcr.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
dcr.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
dcr.bank |
A, B |
The DCR has two banks of inputs identified as Bank A and Bank B. Each bank has 16 input channels each. The Bank is normally defaulted to the correct one for the front-end in use, but check with the telescope operator or receiver engineer, if you are uncertain. |
dcr.testtone |
Off, On |
A 5 MHz test signal is available for testing the DCR input channels. When turned on this signal DISCONNECTS THE V/F INPUTS FROM THE RECEIVER. Five MHz is about half of the maximum V/F frequency and about 5 times the typical input frequency of 1 MHz. This is a spring-loaded variable in the sense that it is reset to 'off' after each scan. |
dcr.calstate |
Off, On |
Each Cal toggle button specifies the state of the receiver calibration signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the Cal states are predetermined by the selected mode. |
dcr.sw1 |
Hi , Low |
Each Sw1 toggle button specifies the state of the first optional TTL output port in the button's phase. This port is available for driving devices other than the receiver calibration signal and frequency/load/beam switching in synchronism with these signals. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. The Sw1 states may be set by the user in any selected mode. |
dcr.sw2 |
Hi , Low |
Each Sw2 toggle button specifies the state of the second optional TTL output port in the button's phase. This port is available for driving devices other than the receiver calibration signal and frequency/load/beam switching in synchronism with these signals. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. The Sw2 states may be set by the user in any selected mode. |
dcr.sw3 |
Hi , Low |
Each Sw3 toggle button specifies the state of the third optional TTL output port in the button's phase. This port is available for driving devices other than the receiver calibration signal and frequency/load/beam switching in synchronism with these signals. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. The Sw3 states may be set by the user in any selected mode. |
dcr.sw4 |
Hi , Low |
Each Sw4 toggle button specifies the state of the fourth optional TTL output port in the button's phase. This port is available for driving devices other than the receiver calibration signal and frequency/load/beam switching in synchronism with these signals. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. The Sw4 states may be set by the user in any selected mode. |
dcr.sigrefstate |
Sig, Ref |
Each SigRef toggle button specifies the state of the receiver frequency/load/beam switch signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the SigRef states are predetermined by the selected mode. |
dcr.blankingtime |
|
Banking Time is the time in seconds at the beginning of each switch phase when data integration is inhibited. The Blanking Time may be set to a different value for each phase through the glish command line, but one value is usually sufficient for every phase, and that value is specified here. The resolution in 100nS. |
dcr.chartrecorder1 |
"Chan 1", "Chan 2", "Chan 3", "Chan 4", "Chan 5", "Chan 6", "Chan 7", "Chan 8", "Chan 9", "Chan 10", "Chan 11", "Chan 12", "Chan 13", "Chan 14", "Chan 15", "Chan 16" |
There are two F/V convertor outputs that may be connected to a paper chart recorder. ChartRecorder1 specifies which input V/F channel (1-16) is sent to the first output. |
dcr.chartrecorder2 |
"Chan 1", "Chan 2", "Chan 3", "Chan 4", "Chan 5", "Chan 6", "Chan 7", "Chan 8", "Chan 9", "Chan 10", "Chan 11", "Chan 12", "Chan 13", "Chan 14", "Chan 15", "Chan 16" |
There are two F/V convertor outputs that may be connected to a paper chart recorder. ChartRecorder2 specifies which input V/F channel (1-16) is sent to the second output. |
dcr.monitor1 |
"Chan 1", "Chan 2", "Chan 3", "Chan 4", "Chan 5", "Chan 6", "Chan 7", "Chan 8", "Chan 9", "Chan 10", "Chan 11", "Chan 12", "Chan 13", "Chan 14", "Chan 15", "Chan 16" |
Two input channels may be monitored for out-of-range conditions. Monitor1 specifies the first of the channel selections (1-16). |
dcr.monitor2 |
"Chan 1", "Chan 2", "Chan 3", "Chan 4", "Chan 5", "Chan 6", "Chan 7", "Chan 8", "Chan 9", "Chan 10", "Chan 11", "Chan 12", "Chan 13", "Chan 14", "Chan 15", "Chan 16" |
Two input channels may be monitored for out-of-range conditions. Monitor2 specifies the second of the channel selections (1-16). |
dcr.advancetime |
|
Two of the six switching signals may be advanced in time and sent to separate TTL output ports. These might be used to drive a high-inertia device, such as a secondary or tertiary mirror, to start it moving before the DCR switches phase integrators. The Advance Time specifies the time lead, in seconds between 0 and 0.5, of both of these signals. The Advance Sig1 and Advance Sig2 menu buttons on the Switching Setup panel show or select which of the six signals are advanced and connected to the output ports. |
dcr.advancesig1 |
Cal, S/R, Sw1, Sw2, Sw3, Sw4 |
Two of the six switching signals may be advanced in time and sent to separate TTL output ports. These might be used to drive a high-inertia device, such as a secondary or tertiary mirror, to start it moving before the DCR switches phase integrators. The Advance Sig1 menu button selects which of the six signals are advanced and connected to the first output port. The Advance Time specifies the time lead, in seconds between 0 and 0.5, of both Advance Sig1 and Advance Sig2. |
dcr.advancesig2 |
Cal, S/R, Sw1, Sw2, Sw3, Sw4 |
Two of the six switching signals may be advanced in time and sent to separate TTL output ports. These might be used to drive a high-inertia device, such as a secondary or tertiary mirror, to start it moving before the DCR switches phase integrators. The Advance Sig2 menu button selects which of the six signals are advanced and connected to the second output port. The Advance Time specifies the time lead, in seconds between 0 and 0.5, of both Advance Sig1 and Advance Sig2. |
dcr.numberofphases |
|
The Number of Phases specifies how many phases are in the switching cycle. This number is predetermined by the selected Switching Mode for all but the "User Defined" mode. In that mode the number may be between 1 and 10. |
dcr.switchperiod |
|
The Switch Period specifies the time in seconds of a full switch cycle. The Integration Time must be an integer number of Switch Periods and will be changed to the nearest value when a new Switch Period is entered. |
dcr.cyclesperintegration |
|
Switch Periods per Integration is for information only. It is the Integration Time divided by the Switch Period. The Integration Time is adjusted automatically to make this an integer. |
dcr.integrationtime |
|
Integration Time is the time of one recorded data sample. It is automatically adjusted to be an integer number of Switch Periods. One data sample will contain a separate data integration for each phase in the switching cycle. |
dcr.channel |
|
Any of 16 input channels may be activated by toggling its button to"on" as indicated by its square dot being dark. |
dcr.phasestart |
|
Each Phase Start entry field specifies the beginning of this phase as a fraction of the total switch cycle. The first start time must be zero, they must increase monotonically, and the last phase start time must be less than one. The effective integration time for a phase in one switching cycle is the product of the Switch Period and the difference between that phase's and the next phase's start times minus the Blanking Time. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the phase Start times are predetermined by the selected mode. |
dcr.scannumber |
|
The Scan Number normally updates at the beginning of each scan, but it may be reset by specifying a new value for nextscannumber. The Scan Number itself is read only. |
|
Receiver/Front End Selection (fe)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| fe.receiver |
"0.39 - 0.52", "0.51 - 0.69", "0.68 - 0.92", "1.15 - 1.73", "1.73 - 2.60", "3.95 - 5.85", "8.00 - 10.0", "12.0 - 15.4", "18.0 - 22.0", "22.0 - 26.5", "26.5 - 40.0", "68.0 - 95.0", "90.0 - 115.0" |
The receiver selection assigns a number of parameters with defaults |
|
Local Oscillator (lo1)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| lo1.starttime |
|
The default for starting a scan is to simply start as soon as possible, in which case you should not specify a start time. Start times for procedures must be set with one of the procedure keywords start_utc or start_lst. This LO1 start_time is a lower level parameter for direct control of the LO1 or the scan coordinator. If the Scan Coordinator manager is present this value actually sets the sc.start_time value. The lo1.start_time value is set only when the LO1 is being run in stand-alone mode. UTC is assumed for this parameter.
This keyword can be set directly with the set_sc_parameter() GO glish function using the TimeStamp() glish conversion function:
set_sc_parameter('start_time', TimeStamp(hh, mm, ss, MJD))
where hh:mm:ss is the UTC time, and MJD is the Modified Julian Date. Two routines are provided for the convenience of setting the start_time using the current MJD or by specifying the Local Sidereal Time:
set_sc_start_utc('11:45:36.343')
set_sc_start_lst('02:44:18')
An LST will be converted to UTC, and the time will be assumed to be in the day between the current time minus 30 minutes and plus 23 hours 30 minutes. Note the time format and the fact that they are specified as strings. When you execute the procedure
x := get_sc_parameter('start_time');
the value returned is a glish record containing the Modified Julian Date and the UTC in seconds since the beginning of the day, e.g., [seconds=61714, MJD=51821, flags=0, refFrame=1, units=1].
GO Table Example: lo1.start_time = "[seconds=11987, MJD=52345]" |
lo1.stoptime |
|
The default for starting a scan is to simply start as soon as possible, in which case you should not specify a start time. If you want to specify a stop time for the 'track' procedure you must use one of the procedure keywords stop_utc or stop_lst. This scan coordinator stop_time is a lower level parameter for direct control of the scan coordinator. If the Scan Coordinator manager is present this value actually sets the sc.stop_time value. The lo1.stop_time value is set only when the LO1 is being run in stand-alone mode. UTC is assumed for this parameter.
This keyword can be set directly with the set_sc_parameter() function using the TimeStamp() conversion: set_sc_parameter('stop_time', TimeStamp(hh, mm, ss.s, MJD))
where hh:mm:ss.s is the UTC time, and MJD is the Modified Julian Date. Two routines are provided for the convenience of setting the stop_time using the current MJD or by specifying the Local Sidereal Time:
set_sc_stop_utc('11:45:36.343') set_sc_stop_lst('02:44:18')
An LST will be converted to UTC, and the time will be assumed to be in the day between the current time minus 30 minutes and plus 23 hours 30 minutes. Note the time format and the fact that it is specified as a string. When you execute the procedure
x := get_sc_parameter('stop_time');
the value returned is a glish record containing the Modified Julian Date and the UTC in seconds since the beginning of the day, e.g., [seconds=61714, MJD=51821, flags=0, refFrame=1, units=1].
GO Table Example: lo1.stop_time = "[seconds=59306, MJD=52368]" |
lo1.scanlength |
|
The Scan Length is the duration of the scan in seconds. Any data integrations completed after the end of a scan will normally be discarded. Hence, the Scan Length is typically an integer number of integration times plus a second or two. If the Scan Coordinator manager is present this value actually sets the sc.scan_length value. The lo1.scan_length value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.scan_length = 600.3 |
lo1.nextscannumber |
|
The Scan Number normally updates at the beginning of each scan, but it may be set to a new value by setting the next_scan_number parameter value. If the Scan Coordinator manager is present this value actually sets the sc.next_scan_number value. The lo1.next_scan_number value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.next_scan_number = 99 |
lo1.scannumber |
|
The scan number of the current scan if a scan is being executed, or the scan number of the last completed scan. This value is a read-only parameter. To change the scan number the next_scan_number keyword should be used. |
lo1.projectid |
|
The Project ID is the "number" assigned to your program on the telescope schedule, e.g., GBT01A-011. This string is used as a directory name for your data, e.g. /home/gbtdata/GBT01A-011. If the Scan Coordinator manager is present this value actually sets the sc.project_id value. The lo1.project_id value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.project_id = "GBT01A-011" |
lo1.sourcename |
|
Any Source Name less than 32 characters. In pulsar observing this name is used to fetch the current pulsar timing parameters and must be in a standard 'hhmmsdd' format, e.g., 0329+54, and must match the name in the polyco.dat file. In other observing modes the Source Name is only an identifier label. If the Scan Coordinator manager is present this value actually sets the sc.source_name value. The lo1.source_name value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.source_name = "3C84" |
lo1.scanid |
|
The Scan I.D. is a supplement to the Source Name for labeling the data. It has no effect on the data taking process. The string must be less than 32 characters. If the Scan Coordinator manager is present this value actually sets the sc.scan_id value. The lo1.scan_id value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.scan_id = "3C84 pointing scan" |
lo1.loconfig |
TrackA_TToneB, TrackB_TToneA, TrackA_BNotUsed, TrackB_ANotUsed |
Defines the configuration of LO1A and LO1B. Either LO1A or LO1B can be used as a tracking LO, with the other unused or operating as a test tone generator.
GO Table Example: lo1.lo_config = "TrackA_BNotUsed" |
lo1.defvel |
Radio , Optical , Relativistic |
The velocity definition which specifies how the source velocity is translated into frequency for Doppler tracking. Possible choices are RELATIVISTIC, OPTICAL, RADIO, or Z. If redshift (Z) is chosen then the src_vel keyword will specify the unitless value of the redshift.
N.B. The Z option is not yet implemented in YGOR.
GO Table Example: lo1.def_vel = "RADIO" |
lo1.sourcevelocity |
|
The record containing the epoch and velocity, in units of km/s, which determines the sky frequency of the spectrometer passband. The Doppler correction equations are used to convert this velocity to frequency using the rest frame specified by the velocity definition and reference frame. The record can contain multiple epoch, velocity pairs. The record must be of lenght n times 7 where n is an integer. The first four values in each sequence of seven values define the epoch at which the velocity is defined. The next three values in the sequence define the value of the velocity and its first and second derivatives at the specified epoch. The values in order are hours, minutes, seconds, MJD, velocity, acceleration (d(velocity)/dt) and jerk (d/dtd(velocity)/dt).
This keyword should be used for situations where the source velocity changes during an integration.
GO Table Example: (1st example is for a single epoch and the 2nd example is for two epochs.)
lo1.source_velocity = [1,1,1,51200,120,.001,.00005]
lo1.source_velocity = [1,1,1,51200,120,.001,.00005, 2,2,2,53432,-40.1,-0.002,-0.034] |
lo1.srcvel |
|
The velocity, in units of km/s, which determines the sky frequency of the spectrometer passband. The Doppler correction equations are used to convert this velocity to frequency using the rest frame specified by the velocity definition and reference frame.
GO Table Example: lo1.src_vel = 100.03 |
lo1.subsystemselect |
|
The Subsystem Select parameters determines which of the LO1 subsystems are active to participate in scan sequence. The value for this parameter is a 4-element, boolean array with the elements corresponding, respectively, to the LO1A, LO1B, LO1Counter, and LO1Router.
GO Table example: lo1.subsystem_select = ["T", "T", "F", "T"] |
lo1.subsystemstate |
Off, Standby, Ready, Activating, Committed, Running, Stopping, Aborting, NotInService |
The Subsystem State is a read-only parameter that tells which of the LO1 subsystems are active to participate in scan sequence. The value for this parameter is a 4-element, string array with the elements corresponding, respectively, to the LO1A, LO1B, LO1Counter, and LO1Router. |
lo1.numfswoffsets |
|
The number of frequency switching offsets determines the size of the fsw_offsets array. The number of frequency switching offsets must be larger than zero and less than 5. Changing the number of frequency offsets will change the fsw_offsets array and possibly the values of rest_freq_1 and rest_freq_2.
Go Table Example: lo1.num_fsw_offsets = 2 |
lo1.fswoffsets |
|
An array of the requested frequency offsets in MHz for each signal-refernce phase. For example, to frequency switch using two equal but opposite offsets of 2.5 MHz use fsw_offsets = [0, 2.5, 0, -2.5]. This is equivalent to setting switch_mode = 'FSW_0102', ref_freq_1 = 2.5, and ref_freq_2 = -2.5.
N.B. In order to turn off frequency switching set fsw_offsets = 0 or the num_fsw_offsets parameter must be used and set to zero (it will revert back to a value of one but will set fsw_offsets = 0.
GO Table Examples: lo1.fsw_offsets = [0., 2.5, 0., -2.5]
lo1.fsw_offsets = [0., 5.] |
lo1.reffreq1 |
|
The reference frequency offset 1 in MHz. This keyword is only used when the switching mode is set to one of the frequency switching options.
GO Table Example: ref_freq_1 = -5.0 |
lo1.reffreq2 |
|
The reference frequency offset 2 in MHz. This keyword is only used when the switching mode is set to one of the frequency switching options.
GO Table Example: ref_freq_2 = -5.0 |
lo1.primarysegments |
|
Primary Segments specify the position of the telescope beam on the sky in the selected Coordinate Mode during a scan. Each segment consists of a position and first and second position time derivatives in each of two coordinates, e.g. RA and Dec, and a segment duration. Time is in seconds for the duration and the derivatives. There can be any number of segments, but only the first one is displayed here. One segment is usually enough for most observations, in which case the duration should be equal to the scan length. If the total time given by the Primary Segments is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. The time field displayed is the segment duration.
This parameter is read-only for informative purposes in the LO1. |
lo1.primaryoffsets |
|
Primary Offsets specify telescope beam position offsets during a scan from the positions given by the Primary Segments in the selected Coordinate Mode during a scan. Each segment consists of a position and first and second position time derivatives in each of two coordinates, e.g. RA and Dec, and a segment duration. Time is in seconds for the duration and the derivatives. There can be any number of segments, but only the first one is displayed here. If the total time given primary offsets is greater than the scan length, some of the last segments may be ignored or truncated. If the total segment time is less than the scan length, the last segment will be extrapolated. The time field displayed is the segment duration.
This parameter is read-only for informative purposes in the LO1. |
lo1.primaryunits |
Deg/Deg, Hrs/Deg, Rad/Rad |
The Primary Units parameter specifies the units used by the Primary Segments and Primary Offsets. The choices are Hrs/Deg, Deg/Deg, and Rad/Rad. Hrs/Deg normally only applies to RA/Dec and HA/Dec but can be applied to other coordinates.
This parameter is read-only for informative purposes in the LO1. |
lo1.usertransform |
|
The User Transform specifies a user-defined spherical coordinate system with a three-axis coordinate rotation from the selected coordinate system, e.g. J2000, AzEl, etc. The rotations may be made time dependent, for tracking solar system objects, by specifying first and second derivatives for each rotation component. Also, any number rotation segments may be concatenated, if one parabolic track is not sufficient. The coordinate rotation "track" is independent of scan times and durations, but the segments must span the time of any scans that use the UserDefined Coordinate Mode. The time fields refer to the MJD and UTC, in seconds, for the beginning of the segment. The three coordinate rotations are around the Z, X, and Z axes, in that order. The Z axis is through the positive pole (except for the left-handed AzEl system where it is through the nadir); the X axis is through longitude = latitude = 0; and the Y axis is through longitude = 90 degrees, latitude = 0. The rotations are specified in units determined by the 'primaryunits' parameter with time in seconds for the velocity and acceleration.
This parameter is read-only for informative purposes in the LO1. |
lo1.usertransformorder |
XYX, XYZ, XZX, XZY, YXY, YXZ, YZX, YZY, ZXY, ZXZ, ZYX, ZYZ |
The User Transform Order parameter allows the user to invoke any spherical coordinate rotation from a user defined system to the currently selected coordinate mode. The rotation axes are defined as a right-hand coordinate system, where Z is toward the current pole, and X is toward the zero point on the current equator. For example, you can define a new origin and equator orientation at a J2000 Ra/Dec point with an XYZ rotation order. The X rotation orients the new equator parallel to the J2000 equator, the Y rotation moves the new equator onto the J2000 equator, and the Z rotation moves the new equinox to the J2000 equinox. The rotation order choices are XYX, XYZ, XZX, XZY, YXY, YXZ, YZX, YZY, ZXY, ZXZ, ZYX, and ZYZ
This parameter is read-only for informative purposes in the LO1. |
lo1.usertransformenable |
Off, On |
User Transform Enable determines whether a coordinate rotation, as defined by the User Transform and User Trasnsform Order, is to be done in the selected Coordinate Mode spherical coordinates. This allows you to define a new coordinate origin and pole. For example, you could set the 'equinox' of our coordinates on an object to be mapped and rotate the 'equator' to align with the objects major axis. The user transform is employed to track a solar system object, but the parameters for keeping the origin on the object are computed automatically. To set up a new origin from the GUI panels, select 'User Transform' with the 'Other Panels' button in the Antenna Setup panel. The full user transform parameter is a glish record with as many segments as are required to track a moving object. To set a fixed origin redefinition use the New Origin parameters in the procedures group.
This parameter is read-only for informative purposes in the LO1. |
lo1.cosvmode |
Off, On |
The Cosine Minor parameter controls whether position offsets in the major coordinate (RA, Azimuth, or Longitude) are multiplied by the secant of the minor coordinate (Dec, Elevation, or Latitude). The choices are ON and OFF.
This parameter is read-only for informative purposes in the LO1. |
lo1.coordinatemode |
J2000 , B1950 , RaDecOfDate , ApparentRaDec, Galactic , HaDec , AzEl |
The Coordinate Mode defines the coordinate system in which the direction of the telescope beam is specified. This coordinate system applies to the Primary Segment and Primary Offset parameters and the coordinate system into which the User Transform coordinates are rotated. The available Coodinate Modes are J2000, B1950, RaDecofDate, ApparentRaDec, Galactic, HaDec, and AzEl.
This parameter is read-only for informative purposes in the LO1. |
lo1.offsetcoordinatemode |
J2000 , B1950 , RaDecOfDate , ApparentRaDec, Galactic , HaDec , AzEl |
The Offset Coordinate Mode defines the coordinate system in which the direction of the telescope motion is specified. This coordinate system applies to the Primary Offset parameters. The available Offset Coodinate Modes are J2000, B1950, RaDecofDate, ApparentRaDec, Galactic, HaDec, and AzEl.
This parameter is read-only for informative purposes in the LO1. |
lo1.epoch |
|
This parameter is the epoch of the coordinateMode. Active only when coordinateMode is set to RaDecOfDate. Otherwise this value provides feedback.
This parameter is read-only for informative purposes in the LO1. |
lo1.numberofphases |
|
The Number of Phases specifies how many phases are in the switching cycle. This number is predetermined by the selected Switching Mode for all but the "User Defined" modes. In that mode the number may be between 1 and 64. If the Scan Coordinator manager is present this value actually sets the sc.number_of_phases value. The lo1.number_of_phases value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.nubmer_of_phases = 8 |
lo1.blankingtime |
|
Blanking Time is the time in seconds at the beginning of each switch phase when data integration is inhibited. The Blanking Time may be set to a different value for each phase through the glish command line, but one value is usually sufficient for every phase, and that value is specified here. The resolution in 100nS.If the Scan Coordinator manager is present this value actually sets the sc.blanking_time value. The lo1.blanking_time value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.blanking_time = 0.02 |
lo1.phasestart |
|
Each Phase Start entry field specifies the beginning of this phase as a fraction of the total switch cycle. The first start time must be zero, they must increase monotonically, and the last phase start time must be less than one. The effective integration time for a phase in one switching cycle is the product of the Switch Period and the difference between that phase's and the next phase's start times minus the Blanking Time. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" modes. In all but the "User Defined" modes the phase Start times are predetermined by the selected mode. If the Scan Coordinator manager is present this value actually sets the sc.phase_start value. The lo1.phase_start value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.phase_start = [0.0, 0.25, 0.50, 0.75] |
lo1.calstate |
Off, On |
Each Actual Cal button specifies the state of the receiver calibration signal in the button's switching phase used in the LO1. If the Scan Coordinator manager is present this value actually sets the sc.cal_state value. The lo1.cal_state value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.cal_state = ['ON', 'OFF', 'ON', 'OFF'] |
lo1.sigrefstate |
Sig, Ref |
Each SigRef toggle button specifies the state of the receiver frequency/load/beam switch signal in the button's switching phase. The number of phases depends on the selected Switching Mode or on the number of phases selected by the user in the "User Defined" mode. In all but the "User Defined" mode the SigRef states are predetermined by the selected mode. If the Scan Coordinator manager is present this value actually sets the sc.sig_ref_state value. The lo1.sig_ref_state value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.sig_ref_state = ['Sig', 'Ref','Sig', 'Ref'] |
lo1.switchperiod |
|
The Switch Period specifies the time in seconds of a full switch cycle. The Integration Time must be an integer number of Switch Periods and will be changed to the nearest value when a new Switch Period is entered. If the Scan Coordinator manager is present this value actually sets the sc.switch_period value. The lo1.switch_period value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.switch_period = 2.0 |
lo1.switchingsignalsmaster |
SpectralProcessor, DCR, Spectrometer |
The Switching Signals Master selects which backend provides the switching signals to all of the backends. If the Scan Coordinator manager is present this value actually sets the sc.switching_signals_master value. The lo1.switching_signals_master value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.switching_signals_master = "DCR" |
lo1.receiver |
NoiseSource, "0.290 - 0.395", "0.385 - 0.520", "0.510 - 0.690", "0.680 - 0.920", "0.910 - 1.230", "1.15 - 1.73", "1.73 - 2.60", "3.95 - 5.85", "8.00 - 10.1", "12.0 - 15.4", "18.0 - 22.4", "22.0 - 26.5", "40.0 - 50.0" |
The receiver identifies the "effective front-end" being used for the observations. This allows some control of switching signals during doppler tracking to be automatically setup. It also allows some of the IF chain to be automatically setup.If the Scan Coordinator manager is present this value actually sets the sc.receiver value. The lo1.receiver value is set only when the LO1 is being run in stand-alone mode.
GO Table Example: lo1.receiver = "Rcvr1_2" |
lo1.refframe |
Local , Barycentric , Heliocentric , " LSR (LSRK) ", LSRD , Galactocentric |
Inertial reference frame for Doppler tracking. The source velocity is expressed in terms of the selected rest frame. Possible values are 'Local', 'Barycenteric', 'Heliocentric', 'LSR', 'LSRD', 'Galactocentric', 'Localgroup', and 'CMB'.
Local: local topocentric rest frame of the telescope.
Barycentric: the center of mass of the solar system.
Heliocentric: the center of the Sun.
LSR or LSRK: the kinematical local standard of rest which is a point in the vicinity of the Sun which has the motion of 20 km/s towards RA=18:00:00.0, Dec=30:00:00 (1900).
LSRD: the dynamical local standard of rest which is a point in the vicinity of the Sun in a circular orbit around the Galactic Center. This peculiar motion is 16.6 km/s towards RA=17:49:58.7, Dec=28:07:04 (J2000).
Galactocentric: the Galactic Center and is referenced from the dynamical LSR rest frame assuming the Sun is moving 220 km/s towards Ra=21:12:01.1, Dec=48:19:47 (J2000).
Localgroup: defined as the standard of rest with respect to the Local Group of Galaxies.
CMB: defined as the standard of rest with respect to the Cosmic Microwave Background.
N.B. The Localgroup and CMB reference frames are not yet implemented in the YGOR LO1 manager.
N.B. At some observatories heliocentric really means barycentric. In general there are two different LSR frames: kinematical and dynamical. Since LSR generally corresponds to the kinematical local standard of rest LSR=LSRK. LSRK is derived from "standard solar motion" while LSRD is derived from "basic solar motion."
GO Table Example: lo1.ref_frame = "LSR" |
lo1.restfreq |
|
The frequency with respect to the astronomical object in MHz (i.e., no Doppler correction). For example, observations of the 21cm line of HI would set the rest frequency to 1420.4058 MHz. For continuum observerations it is the sky center frequency of the final passband when Doppler tracking is not required. In continuum observations, the following should also be set: ref_frame = LOCAL, vel_def = RADIO, and src_vel = 0.
GO Table Example: lo1.rest_freq = 1420.4058 |
lo1.tolerance |
|
The desired frequency tolerance in Hz for Doppler updates. The minimum value is 1 Hz.
GO Table Example: lo1.tolerance = 10.0 |
lo1.testtonefreq |
|
The frequency of the testtone signal in MHz.
GO Table Example: lo1.testtone_freq = 1245.67 |
lo1.ifcenterfreq |
|
The desired IF center frequency after the first mixer (LO1) in MHz. Effectively the sky frequency and the IF center frequency are used to determine the LO1 frequency. This value depends on the front end recevier chosen and will be set by default to the following values when the recevier is selected:
Effective Receiver IF Center Freq.
0.290 - 0.395 GHz 1080 MHz
0.385 - 0.520 GHz 1080 MHz
0.510 - 0.690 GHz 1080 MHz
0.680 - 0.920 GHz 1080 MHz
0.910 - 1.230 GHz 1080 MHz
1.15 - 1.73 GHz 3000 MHz
1.73 - 2.60 GHz 6000 MHz
3.95 - 5.85 GHz 3000 MHz
8.0 - 10.1 GHz 3000 MHz
12.0 - 15.4 GHz 3000 MHz
18.0 - 22.4 GHz 6000 MHz
22.0 - 26.5 GHz 6000 MHz
40.0 - 50.0 GHz 6000 MHz
These default values may be overridden, however, by using the 'if_center_frequency' parameter.
GO Table Example: lo1.if_center_freq = 3000.0 |
lo1.sideband |
lower, upper, testtone |
The LO1 synthesizer sideband. Possible values are 'upper' or 'lower'. The sideband will be set by default when the effective receiver is selected using the following values:
Effective Receiver sideband
0.290 - 0.395 GHz (lower),
0.385 - 0.520 GHz (lower),
0.510 - 0.690 GHz (lower),
0.680 - 0.920 GHz (lower),
0.910 - 1.230 GHz (lower),
1.15 - 1.73 GHz (lower),
1.73 - 2.60 GHz (lower),
3.95 - 5.85 GHz (lower),
8.0 - 10.1 GHz (lower),
12.0 - 15.4 GHz (upper),
18.0 - 22.4 GHz (upper),
22.0 - 26.5 GHz (upper),
40.0 - 50.0 GHz (upper).
The sideband parameter automatically sets both the sideband_a and sideband_b keyword values to the current value of sideband.
GO Table Example: lo1.sideband_a = 'upper' |
lo1.powerlevel |
|
The LO1 synthesizer output power level in dBm. This is typically set automatically using the auto_power_level parameter when a receiver is selected. Possible values range from -20 to +13.5dBm.
GO Table Example: lo1.power_level = 2.5 |
lo1.autopowerlevel |
On , Off |
Enables LO1 automatic power level setting. If set to 'ON' the LO1 synthesizer output power level will be set automatically depending on the selected receiver. Otherwise if 'OFF' the parameter 'power_level' is used to set the output power level. The automatic power level is optimized from previous experience for each receiver.
GO Table Example: lo1.auto_power_level = "ON" |
lo1.testtonepowerlevel |
|
The testtone synthesizer output power level in dBm. Possible values range from -20 to +13.5dBm.
GO Table Example: lo1.testtone_power_level = 2.5 |
lo1.useoffsets |
On , Off |
A boolean to determine if the offset positions are used to when calculating frequency information (e.g., Doppler tracking). The default setting is 'T'.
GO Table Example: lo1.use_offsets = "T" |
lo1.multipliera |
|
This parameter is the external LO frequency multiplier. Some receivers require that the internally generated LO1 frequency be doubled, etc. before reaching the requested LO frequency to be mixed with the receiver's sky frequency in order to produce the desired IF frequency. This parameter is used internally in the LO generation and should typically be ignored in the general LO equations.
This parameter is provided only for informational purposes. |
lo1.looffseta |
|
This parameter is the external LO frequency offset term for LO equation in MHz. Some receivers require that the internally generated LO frequency be mixed with a fixed frequency from a crystal oscillator in order to produce the desired LO frequency. This parameter indicates how much the internal LO frequency has been shifted (offset) during this procedure.
This parameter is provided only for informational purposes. |
lo1.powerlevela |
|
The LO1A synthesizer output power level in dBm. This is typically set automatically using the auto_power_level parameter when a receiver is selected. Possible values range from -20 to +13.5dBm.
GO Table Example: lo1.power_level_a = 2.5 |
lo1.sidebanda |
lower, upper, testtone |
The LO1A synthesizer sideband. Possible values are 'upper' or 'lower'. The sideband will be set by default when the effective receiver is selected using the following values:
Effective Receiver sideband
0.290 - 0.395 GHz (lower),
0.385 - 0.520 GHz (lower),
0.510 - 0.690 GHz (lower),
0.680 - 0.920 GHz (lower),
0.910 - 1.230 GHz (lower),
1.15 - 1.73 GHz (lower),
1.73 - 2.60 GHz (lower),
3.95 - 5.85 GHz (lower),
8.0 - 10.1 GHz (lower),
12.0 - 15.4 GHz (upper),
18.0 - 22.4 GHz (upper),
22.0 - 26.5 GHz (upper),
40.0 - 50.0 GHz (upper).
GO Table Example: lo1.sideband_a = 'upper' |
lo1.lomodea |
tracking, testtone |
The operational mode LO1A. This mode can be either "tracking" or "testtone". In tracking mode the LO1A is being used to generate the LO signal for the receiver. In testtone mode is is either not being used or is being used to generate a test tone signal depending on the value of the lo_config parameter.
This parameter is provided only for informational purposes. |
lo1.multiplierb |
|
This parameter is the external LO frequency multiplier. Some receivers require that the internally generated LO1 frequency be doubled, etc. before reaching the requested LO frequency to be mixed with the receiver's sky frequency in order to produce the desired IF frequency. This parameter is used internally in the LO generation and should typically be ignored in the general LO equations.
This parameter is provided only for informational purposes. |
lo1.looffsetb |
|
This parameter is the external LO frequency offset term for LO equation in MHz. Some receivers require that the internally generated LO frequency be mixed with a fixed frequency from a crystal oscillator in order to produce the desired LO frequency. This parameter indicates how much the internal LO frequency has been shifted (offset) during this procedure.
This parameter is provided only for informational purposes. |
lo1.powerlevelb |
|
The LO1B synthesizer output power level in dBm. This is typically set automatically using the auto_power_level parameter when a receiver is selected. Possible values range from -20 to +13.5dBm.
GO Table Example: lo1.power_level_b = 2.5 |
lo1.sidebandb |
lower, upper, testtone |
The LO1B synthesizer sideband. Possible values are 'upper' or 'lower'. The sideband will be set by default when the effective receiver is selected using the following values:
Effective Receiver sideband
0.290 - 0.395 GHz (lower),
0.385 - 0.520 GHz (lower),
0.510 - 0.690 GHz (lower),
0.680 - 0.920 GHz (lower),
0.910 - 1.230 GHz (lower),
1.15 - 1.73 GHz (lower),
1.73 - 2.60 GHz (lower),
3.95 - 5.85 GHz (lower),
8.0 - 10.1 GHz (lower),
12.0 - 15.4 GHz (upper),
18.0 - 22.4 GHz (upper),
22.0 - 26.5 GHz (upper),
40.0 - 50.0 GHz (upper).
GO Table Example: lo1.sideband_b = 'upper' |
lo1.lomodeb |
tracking, testtone |
The operational mode LO1B. This mode can be either "tracking" or "testtone". In tracking mode the LO1B is being used to generate the LO signal for the receiver. In testtone mode is is either not being used or is being used to generate a test tone signal depending on the value of the lo_config parameter.
This parameter is provided only for informational purposes. |
lo1.counterband |
"band 1", "band 2", "band 3" |
This parameter determines which band the frequency counter will use.
GO Table Example: lo1.counter_band = "band 1" |
lo1.counterresolution |
"1 Hz", "10 Hz", "100 Hz", "1 kHz", "10 kHz" |
Resolution of the counter and by extension the sample rate.
GO Table Example: lo1.counter_resolution = "10 Hz" |
lo1.phasecalctrl |
On , Off |
Controls the operation of phase CAL for the LO1. CAL is short for calibration and corresponds to a series of "rails" injected into the system for calibration purposes. This is primarily used for VLBI observations.
GO Table Example: lo1.phase_cal_ctrl = "On" |
lo1.phasecalmode |
"5 MHz", "1 MHz" |
The Phase Cal "rail" injection can occur with the rails spaced every 5 MHz or every 1 MHz. This parameter allows the selection of the rail spacing to be set.
GO Table Example: lo1.phase_cal_mode = "5 MHz" |
lo1.s1 |
thru, cross |
A copy of the LO1A and LO1B synthesizer frequencies are available to be routed to the LO Counter or to the Test Tone outputs of the LO1 rack. One input signal (LO1A or LO1B generated) into the S1 switch is routed on to be available for the LO Counter or the Test Tone outputs (via the S3 switch) while the other input signal into the S1 switch is terminated to ground. When the S1 switch is in the "thru" position the LO1B generated signal is terminated to ground while the LO1A generated signal is routed on to the S3 switch. When the S1 switch is in the "cross" position the LO1A generated signal is terminated to ground while the LO1A generated signal is routed on to the S3 switch. The signal routed on to the S3 switch will be refered to as the "LO monitor signal".
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s1 = "thru" |
lo1.s2 |
thru, cross |
A copy of the LO1A and LO1B synthesizer frequencies are available to be routed to the reciever LO inputs. One input signal (LO1A or LO1B generated) into the S2 switch is routed on to be available to the LO receiver output ports 1-18 of the LO1 rack (via the S4 and S5, S6 & S7 switches) while the other input signal into the S2 switch is routed on to be available to the LO receiver output ports 19-24 of the LO1 rack (via the S8 switch). When the S2 switch is in the "thru" position the LO1A generated signal is routed on to the S4 switch while the LO1B generated signal is routed on to the S8 switch. When the S2 switch is in the "cross" position the LO1B generated signal is routed on to the S4 switch while the LO1A generated signal is routed on to the S8 switch. The signal routed on to the S4 switch will be refered to as the "LO signal".
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s2 = "cross" |
lo1.s3 |
"0 : Unknown ", "1 : Low Band Counter ", "2 : High Band Counter", "3 : Test Tone signal ", "4 : Ground " |
Either of the LO1A or the LO1B generated LO signals (the "LO monitor signal") can be available to be routed to the LO Counter or the Test Tone outputs of the LO1 rack. The S3 switch determines where the LO monitor signal is routed. The S3 switch can be in 5 different positions labeled numerically by an integer in the range 0 to 4. When the S3 switch is set to 0 (zero) there is no power on the LO monitor signal and the S3 switch is in a "undefined" state. When the S3 switch is set to 1 the LO monitor signal is sent to the High Resolution LO Counter. When the S3 switch is set to 2 the LO monitor signal is sent to the Low Resolution LO Counter. When the S3 switch is set to 3 the LO monitor signal is made available to the Test Tone outputs by routing the LO monitor signal to the S11 switch. When the S3 switch is set to 4 the LO monitor signal is terminated to ground.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s3 = 2 |
lo1.s4 |
"0 : Unknown ", "1 : Switch 5", "2 : Switch 6", "3 : Switch 7", "4 : Ground " |
Either of the LO1A or the LO1B generated LO signals (the "LO signal") can be available to be routed to the LO reciever output ports 1-24 of the LO1 rack. The S4 switch determines where the LO signal is routed. The S4 switch can be in 5 different positions labeled numerically by an integer in the range 0 to 4. When the S4 switch is set to 0 (zero) there is no power on the LO signal and the S4 switch is in a "undefined" state. When the S4 switch is set to 1 the LO signal is sent to the LO reciever output ports 1-6 of the LO1 rack via the S5 switch. When the S4 switch is set to 2 the LO signal is sent to the LO reciever output ports 7-12 of the LO1 rack via the S6 switch. When the S4 switch is set to 3 the LO signal is sent to the LO reciever output ports 13-18 of the LO1 rack via the S7 switch. When the S4 switch is set to 1 the LO signal is terminated to ground.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s4 = 2 |
lo1.s5 |
"0 : Unknown ", "1 : LO output 1", "2 : LO output 2", "3 : LO output 3", "4 : LO output 4", "5 : LO output 5", "6 : LO output 6" |
The S5 switch routes the LO signal output from the S4 switch to one of the LO receiver output ports (1-6) of the LO1 rack. The S5 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S5 switch is set to 0 (zero) there is no power on the LO signal and the S5 switch is in a "undefined" state. When the S5 switch is set to 1 the LO signal is sent to the LO reciever output port 1 of the LO1 rack. When the S5 switch is set to 2 the LO signal is sent to the LO reciever output port 2 of the LO1 rack. When the S5 switch is set to 3 the LO signal is sent to the LO reciever output port 3 of the LO1 rack. When the S5 switch is set to 4 the LO signal is sent to the LO reciever output port 4 of the LO1 rack. When the S5 switch is set to 5 the LO signal is sent to the LO reciever output port 5 of the LO1 rack. When the S5 switch is set to 6 the LO signal is sent to the LO reciever output port 6 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s5 = 2 |
lo1.s6 |
"0 : Unknown ", "1 : LO output 7", "2 : LO output 8", "3 : LO output 9", "4 : LO output 10", "5 : LO output 11", "6 : LO output 12" |
The S6 switch routes the LO signal output from the S4 switch to one of the LO receiver output ports (7-12) of the LO1 rack. The S6 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S6 switch is set to 0 (zero) there is no power on the LO signal and the S6 switch is in a "undefined" state. When the S6 switch is set to 1 the LO signal is sent to the LO reciever output port 7 of the LO1 rack. When the S6 switch is set to 2 the LO signal is sent to the LO reciever output port 8 of the LO1 rack. When the S6 switch is set to 3 the LO signal is sent to the LO reciever output port 9 of the LO1 rack. When the S6 switch is set to 4 the LO signal is sent to the LO reciever output port 10 of the LO1 rack. When the S6 switch is set to 5 the LO signal is sent to the LO reciever output port 11 of the LO1 rack. When the S6 switch is set to 6 the LO signal is sent to the LO reciever output port 12 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s6 = 2 |
lo1.s7 |
"0 : Unknown ", "1 : LO output 13", "2 : LO output 14", "3 : LO output 15", "4 : LO output 16", "5 : LO output 17", "6 : LO output 18" |
The S7 switch routes the LO signal output from the S4 switch to one of the LO receiver output ports (13-18) of the LO1 rack. The S7 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S7 switch is set to 0 (zero) there is no power on the LO signal and the S7 switch is in a "undefined" state. When the S7 switch is set to 1 the LO signal is sent to the LO reciever output port 13 of the LO1 rack. When the S7 switch is set to 2 the LO signal is sent to the LO reciever output port 14 of the LO1 rack. When the S7 switch is set to 3 the LO signal is sent to the LO reciever output port 15 of the LO1 rack. When the S7 switch is set to 4 the LO signal is sent to the LO reciever output port 16 of the LO1 rack. When the S7 switch is set to 5 the LO signal is sent to the LO reciever output port 17 of the LO1 rack. When the S7 switch is set to 6 the LO signal is sent to the LO reciever output port 18 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s7 = 2 |
lo1.s8 |
"0 : Unknown ", "1 : LO output 19", "2 : LO output 20", "3 : LO output 21", "4 : LO output 22", "5 : LO output 23", "6 : LO output 24" |
Either of the LO1A or the LO1B generated LO signals (the "LO signal") can be available to be routed to the LO reciever output ports 19-24 of the LO1 rack. The S8 switch determines where the LO signal output from the S2 switch is routed. The S8 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S8 switch is set to 0 (zero) there is no power on the LO signal and the S8 switch is in a "undefined" state. When the S8 switch is set to 1 the LO signal is sent to the LO reciever output port 19 of the LO1 rack. When the S8 switch is set to 2 the LO signal is sent to the LO reciever output port 20 of the LO1 rack. When the S8 switch is set to 3 the LO signal is sent to the LO reciever output port 21 of the LO1 rack. When the S8 switch is set to 4 the LO signal is sent to the LO reciever output port 22 of the LO1 rack. When the S8 switch is set to 5 the LO signal is sent to the LO reciever output port 23 of the LO1 rack. When the S8 switch is set to 6 the LO signal is sent to the LO reciever output port 24 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s8 = 2 |
lo1.s9 |
"0 : Unknown", "1 : LO1A ", "2 : Unknown" |
The S9 switch determines which synthesizer is used to generate the LO1A LO signal. The S9 switch can be in 3 different positions labeled numerically by an integer in the range 0 to 2. When the S9 switch is set to 0 (zero) there is no power on the LO1A LO signal (no synthesizer is selected) and the S9 switch is in a "undefined" state. When the S9 switch is set to 1 the LO signal is derived from the LO1A synthesizer. When the S9 switch is set to 2 the LO signal is derived from a second (user supplied?) synthesizer. Typically there will not be a synthesizer available other than the LO1A synthesizer.
sent to the LO reciever output port 24 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s9 = 1 |
lo1.s10 |
"0 : Unknown", "1 : LO1B ", "2 : Unknown" |
The S10 switch determines which synthesizer is used to generate the LO1A LO signal. The S10 switch can be in 3 different positions labeled numerically by an integer in the range 0 to 2. When the S10 switch is set to 0 (zero) there is no power on the LO1A LO signal (no synthesizer is selected) and the S10 switch is in a "undefined" state. When the S10 switch is set to 1 the LO signal is derived from the LO1A synthesizer. When the S10 switch is set to 2 the LO signal is derived from a second (user supplied?) synthesizer. Typically there will not be a synthesizer available other than the LO1A synthesizer.
sent to the LO reciever output port 24 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s10 = 1 |
lo1.s11 |
thru, cross |
Either the output of the S3 switch (the "LO monitor signal") or the output of the Phase Cal generator can be used to provide a Test Tone for the reciever Test Tone output ports of the LO1 rack, via the S12, S13, S14 and S15 switches. The S11 switch determines whether the LO monitor signal or the Phase Cal signal is used as the Test Tone signal. When the S11 switch is in the "thru" state the LO monitor signal is terminated to ground and the Phase Cal signal is used for the Test Tone signal and is routed on to the S12 switch. When the S11 switch is in the "cross" state the Phase Cal signal is terminated to ground and the LO monitor signal is used for the Test Tone signal and is routed on to the S12 switch.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s11 = "cross" |
lo1.s12 |
"0 : Unknown ", "1 : Ground ", "2 : Ground ", "3 : Switches 14 & 15", "4 : Switch 13 " |
The S12 switch determines where the Test Tone signal is routed. The S12 switch can be in 5 different positions labeled numerically by an integer in the range 0 to 4. When the S12 switch is set to 0 (zero) there is no power on the Test Tone signal and the S12 switch is in a "undefined" state. When the S12 switch is set to 1 the Test Tone signal is terminated to ground. When the S12 switch is set to 2 the Test Tone signal is terminated to ground. When the S12 switch is set to 3 the Test Tone signal is routed to the Test Tone output ports 1-12 of the LO1 rack via the S14 and S15 switches. When the S12 switch is set to 4 the Test Tone signal is routed to the Test Tone output ports 13-18 of the LO1 rack via the S13 switch.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s12 = 2 |
lo1.s13 |
"0 : Unknown ", "1 : TT output 13", "2 : TT output 14", "3 : TT output 15", "4 : TT output 16", "5 : TT output 17", "6 : TT output 18" |
The S13 switch routes the Test Tone signal output from the S13 switch to one of the Test Tone output ports (13-18) of the LO1 rack. The S13 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S13 switch is set to 0 (zero) there is no power on the Test Tone signal and the S13 switch is in a "undefined" state. When the S13 switch is set to 1 the Test Tone signal is sent to the Test Tone output port 13 of the LO1 rack. When the S13 switch is set to 2 the Test Tone signal is sent to the Test Tone output port 14 of the LO1 rack. When the S13 switch is set to 3 the Test Tone signal is sent to the Test Tone output port 15 of the LO1 rack. When the S13 switch is set to 4 the Test Tone signal is sent to the Test Tone output port 16 of the LO1 rack. When the S13 switch is set to 5 the Test Tone signal is sent to the Test Tone output port 17 of the LO1 rack. When the S13 switch is set to 6 the Test Tone signal is sent to the Test Tone output port 18 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s13 = 2 |
lo1.s14 |
"0 : Unknown ", "1 : TT output 1", "2 : TT output 2", "3 : TT output 3", "4 : TT output 4", "5 : TT output 5", "6 : TT output 6" |
The S14 switch routes the Test Tone signal output from the S12 switch to one of the Test Tone output ports (1-6) of the LO1 rack. The S14 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S14 switch is set to 0 (zero) there is no power on the Test Tone signal and the S14 switch is in a "undefined" state. When the S14 switch is set to 1 the Test Tone signal is sent to the Test Tone output port 1 of the LO1 rack. When the S14 switch is set to 2 the Test Tone signal is sent to the Test Tone output port 2 of the LO1 rack. When the S14 switch is set to 3 the Test Tone signal is sent to the Test Tone output port 3 of the LO1 rack. When the S14 switch is set to 4 the Test Tone signal is sent to the Test Tone output port 4 of the LO1 rack. When the S14 switch is set to 5 the Test Tone signal is sent to the Test Tone output port 5 of the LO1 rack. When the S14 switch is set to 6 the Test Tone signal is sent to the Test Tone output port 6 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s14 = 2 |
lo1.s15 |
"0 : Unknown ", "1 : TT output 7", "2 : TT output 8", "3 : TT output 9", "4 : TT output 10", "5 : TT output 11", "6 : TT output 12" |
The S15 switch routes the Test Tone signal output from the S12 switch to one of the Test Tone output ports (7-12) of the LO1 rack. The S15 switch can be in 7 different positions labeled numerically by an integer in the range 0 to 6. When the S15 switch is set to 0 (zero) there is no power on the Test Tone signal and the S15 switch is in a "undefined" state. When the S15 switch is set to 1 the Test Tone signal is sent to the Test Tone output port 7 of the LO1 rack. When the S15 switch is set to 2 the Test Tone signal is sent to the Test Tone output port 8 of the LO1 rack. When the S15 switch is set to 3 the Test Tone signal is sent to the Test Tone output port 9 of the LO1 rack. When the S15 switch is set to 4 the Test Tone signal is sent to the Test Tone output port 10 of the LO1 rack. When the S15 switch is set to 5 the Test Tone signal is sent to the Test Tone output port 11 of the LO1 rack. When the S15 switch is set to 6 the Test Tone signal is sent to the Test Tone output port 12 of the LO1 rack.
One should consult the "cabling file" to determine how signals propagate between devices from a given output port to a given input port.
GO Table Example: lo1.s15 = 2 |
lo1.state |
|
The State is a read-only parameter that shows the current state of the LO1. The state between scans is normally Ready. The scan sequence of State is Activating, Committed, Running, and Stopping in that order. If the State shows Off or Standby, the LO1 may be put into the ready state with the 'lo1.on()' glish command or by using the Scan Coordinator GUI to active the LO1. Normally the LO1 will be Ready when using this panel. When the LO1 is run in stand-alone mode, a scan may be started by pressing the Start button and stopped before its normal termination by pressing the same button which will be labeled Stop while the scan is running. Setup parameters may be changed only in the Ready state. |
lo1.status |
|
The Status is a read-only parameter that tells the currently highest warning or fault level for the LO1. The possible values are clear, Info, Notice, Warning, Error, Fault, and Fatal. One of the last three conditions can prevent the scan sequence from proceeding. |
lo1.actualstarttime |
|
The Actual Start Time is a read only parameter whose value is the UTC time and date of the when the current or last scan actually started. |
|
Analog Filter Rack (algfilt)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| algfilt.starttime |
|
|
algfilt.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
algfilt.scanlength |
|
|
algfilt.nextscannumber |
|
|
algfilt.scannumber |
|
|
algfilt.projectid |
|
|
algfilt.sourcename |
|
|
algfilt.scanid |
|
|
algfilt.subsystemselect |
On , Off |
Turns subsystems on or off in the Analog Filter Rack. |
algfilt.subsystemState |
Off, Standby, Ready, Activating, Committed, Running, Stopping, Aborting, NotInService |
Analog Filter Rack subsystem current state |
algfilt.sginput |
1, 2, 3, 4 |
Selects input from 1-8 GHz Converter Modules |
algfilt.sgfilter |
wide, narrow, spare, external |
Selects output filter. |
algfilt.cffilter |
wide, narrow, spare, external |
Selects filter. |
algfilt.defaultsamplerate |
mr100MS, mr200MS, mr500MS, mr1Sec, mr2Sec, mr5Sec, mr10Sec, mr30Sec, mr1Min, mr2Min, mr5Min, mr10Min, mr30Min, mr1Hr |
Sets the rate at which the sampler is run. |
algfilt.oneppsenable |
On , Off |
Controls 1PPS synchronization. |
algfilt.state |
|
|
algfilt.status |
|
|
|
IF Rack (ifrack)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| ifrack.starttime |
|
|
ifrack.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
ifrack.scanlength |
|
|
ifrack.nextscannumber |
|
|
ifrack.scannumber |
|
|
ifrack.projectid |
|
|
ifrack.sourcename |
|
|
ifrack.scanid |
|
|
ifrack.powersuppliesstatus |
off, ok, warning, fault |
Summary of status of the power voltages. |
ifrack.subsystemselect |
On , Off |
Turns subsystems on or off in the IF Rack. |
ifrack.subsystemstate |
Off, Standby, Ready, Activating, Committed, Running, Stopping, Aborting, NotInService |
Analog Filter Rack subsystem current state |
ifrack.laserpower |
swOff, swOn |
Laser power switches for laser transmitters. |
ifrack.attenuator |
|
0dB - 31dB attenuators for laser transmitters. |
ifrack.analogpowerlevel |
|
Sets the target levels in volts for the laser transmitters. |
ifrack.balance |
Yes, No |
Initiates balancing of the power levels for selected laser transmitter. |
ifrack.balanceselect |
On , Off |
Selects laser transmitters for balancing. |
ifrack.noisesource |
Off, On |
Noise source on/off switch for input to IF routers. |
ifrack.noisebandwidth |
broadband, narrowband |
Noise source bandwidth control. |
ifrack.s1 |
|
Selects one of IF-1 thru IF-8. |
ifrack.s2 |
|
Selects one of IF-9 thru IF-16. |
ifrack.s3 |
|
Selects one of IF-17 thru IF-24. |
ifrack.s4 |
|
Selects one of IF-25 thru IF-32. |
ifrack.s5 |
|
Selects one of IF-33 thru IF-40. |
ifrack.s6 |
|
Selects one of IF-41 thru IF-48. |
ifrack.s7 |
|
Selects one of IF-49 thru IF-56. |
ifrack.s8 |
|
Selects one of IF-57 thru IF-64. |
ifrack.s9 |
thru, cross |
Crosses or passes outputs of S1 and S2. |
ifrack.s10 |
thru, cross |
Crosses or passes outputs of S3 and S4. |
ifrack.s11 |
thru, cross |
Crosses or passes outputs of S5 and S6. |
ifrack.s12 |
thru, cross |
Crosses or passes outputs of S7 and S8. |
ifrack.filterselect |
pass_all, pass_2990_3010, pass_2960_3040, pass_2840_3160, pass_2360_3640, pass_5960_6040, pass_5840_6160, pass_5360_6640 |
Selects among 8 bandpass filter options. |
ifrack.laserautolevelcontrol |
swOn, swOff |
Laser power switches for laser automatic level control. |
ifrack.defaultsamplerate |
mr100MS, mr200MS, mr500MS, mr1Sec, mr2Sec, mr5Sec, mr10Sec, mr30Sec, mr1Min, mr2Min, mr5Min, mr10Min, mr30Min, mr1Hr |
Sets the rate at which the sampler is run. |
ifrack.state |
|
|
ifrack.status |
|
|
|
Prime Focus Support Rack (pfsup)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| pfsup.starttime |
|
|
pfsup.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
pfsup.scanlength |
|
|
pfsup.nextscannumber |
|
|
pfsup.scannumber |
|
|
pfsup.projectid |
|
|
pfsup.sourcename |
|
|
pfsup.scanid |
|
|
pfsup.state |
|
|
pfsup.status |
|
|
|
Prime Focus Support Rack (pfsup)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
|
Calibrator Source Lookup Table (cal)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| cal.search_ra |
|
RA is the Right Ascension in hh mm ss.sss or hh:mm:ss.sss |
cal.search_dec |
|
DEC is the Declination in sdd mm ss.ss or sdd:mm:ss.ss |
cal.search_epoch |
|
EPOCH is the epoch for the specified coordinates. Currently, only J2000 coordinates are accepted. |
cal.cont_catalog |
"NVSS V2.2" |
CATALOG is the continuum catalog used for the search. Currently, only the NVSS catalog is available. |
cal.search_option |
Radius, "RaDec Range", "IAU Name", "Common Name" |
SEARCH is the method used to search the continuum catalog. Search the catalog using the IAU Name, Common Name, by radius, or by RA-Dec ranges. The NVSS catalog currently has no Common Names. |
cal.iau_name |
|
IAU NAME is the IAU name of the calibrator in hhmm+ddmm. |
cal.common_name |
|
COMMON NAME is the common name for the calibrator. For example, 3C84 |
cal.search_radius |
|
SEARCH RADIUS is the calibrator search radius in degrees. |
cal.search_ra_range |
|
RA RANGE is the calibrator ra search range in degrees. |
cal.search_dec_range |
|
DEC RANGE is the calibrator dec search range in degrees. |
cal.search_freq |
|
FREQUENCY is the calibrator search frequency in GHz. |
cal.beam_size |
|
BEAM SIZE is the resolution used to select point sources in arcsec. This selection criterion will only be applied to the NVSS catalog. Note: For the GBT the FWHM beamsize is (720 [arcsec] / Freq [GHz]) |
cal.flux_limit |
|
FLUX LIMIT is the flux density limit for the calibrator search. |
cal.flux_src |
|
SOURCE is the flux density calibrator source name. Measured objects are shown in the calibrator list. |
cal.flux_freq |
|
FREQUENCY is the flux density calibrator frequency requested. The acceptable range of frequencies are displayed in the calibrator list. |
cal.flux_flux |
|
FLUX is the flux density of the calibrator. If zero is displayed then the frequency is outside of the frequency range measured. Table 5 of Ott et al. 1994, A&A, 284, 331 is used to calculate the flux densities. |
cal.psr_name |
|
PSR NAME is either the B1950 or J2000 pulsar name. |
cal.psr_epoch |
B1950, J2000 |
Epoch is the Coordinate epoch or the epoch for the pulsar name -- Either B1950 or J2000. |
cal.control_flag |
Enabled , Disabled |
The Control button determines whether this panel has control of the device to which it is attached or is just reflecting the current device parameters. Enabling control may send parameters or control commands to the device, so be sure that it is not in use by someone else. |
|
Berkley-CalTech Pulsar Machine (bcpm)
|
|
|
|
|
Keyword |
Possible Values |
Description |
|
| bcpm.starttime |
|
The Start Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the time mode with the menu button. In a.s.a.p. mode the time display is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. |
bcpm.stoptime |
|
The Stop Time may be explicitly specified in UTC or LST, or it may simply be as-soon-as-possible. Select the start or stop mode and the type of time with the menu buttons. In a.s.a.p. mode the time displayed is what was actually used for the last scan. Normally the date, and hence the MJD, is implied from the current date. Times are assumed to be in the interval between 1/2 hour before and 23 1/2 hours after the current time. The date may be explicitly set in UTC mode only by unlocking the Date/MJD fields with the glish command "set_mjd_auto(F)". The date may be entered in either mm/dd/yy or MJD format. Use "set_mjd_auto(T)" to relock it. LST times ignore the date settings and use the current date. In Stop Time mode the scan start as soon possible. |
bcpm.scanlength |
|
|
bcpm.nextscannumber |
|
|
bcpm.scannumber |
|
|
bcpm.projectid |
|
|
bcpm.sourcename |
|
|
bcpm.scanid |
|
|
bcpm.operatingmode |
search, voltage_sampling, timing, monitor |
This selects the mode of operation of the BCPM. |
bcpm.submanagersused |
BCPM1, BCPM2, "BCPM1 & BCPM2" |
This selects the used of submanagers of the BCPM. |
bcpm.sumpolarizations |
Powers, Stokes, Voltages |
This flag indicates if the polarizations should be summed in the BCPM |
bcpm.calusedflag |
Yes, No |
This flag indicates if the used_flag should be calmed in the BCPM |
bcpm.datastorage |
Disk, Tape |
This flag indicates the media type for data storage of BCPM generatedpulsar data. |
bcpm.voltageregister |
POLA0, POLA1, POLA2, POLA3, POLB4, POLB5, POLB6, POLB7, Not_Used |
This flag indicates the register from which to sample voltages in the voltage sampling mode of the BCPM |
bcpm.sampletime |
X1, X2, X4, X8 |
Reduction time for reducing the time and/or frequency resolution in the BCPM |
bcpm.samplechoice |
"Total Power", Voltage, None |
Reduction factor for reducing the time and/or frequency resolution in the BCPM |
bcpm.timingtype |
cal, demo, pulsar |
Which sub-mode of BCPM timing mode is to be used. |
bcpm.channelbandwidth |
"1.74 MHz", "1.40 MHz", "1.00 MHz", "0.70 MHz", "0.50 MHz", "0.35 MHz", "0.25 MHz" |
This parameter is the bandwidth for the channels used in BCPM1 andBCPM2 respectively. |
bcpm.numberphasebins |
16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192 |
Number of bins across the pulsar's pulse period. |
bcpm.period |
|
Period of the pulsar (milliseconds) under observation using the BCPM. |
bcpm.dispersionmeasure |
|
Dispersion Measure of the pulsar under observation using the BCPM. |
bcpm.filesize |
|
Sky File size. |
bcpm.centerfrequency |
|
Center frequency of IF going into BCPM. |
bcpm.targetname |
|
Right Ascension |
bcpm.basename |
|
Right Ascension |
bcpm.state |
|
|
bcpm.status |
|
|
|