| <<O>> Difference Topic ScanTypes (r1.69 - 04 Aug 2008 - MelindaMello) |
| Added: | |
| > > |
AutoOOF |
| Changed: | |
| < < | The intent of this scan is to automatically peak and/or focus the antenna for the current location on the sky and with the current receiver, therefore it should not require any user input. However, by setting any of the optional arguments the user may partially or fully override the the calibration search and/or procedural steps as described below. |
| > > | The intent of these scans are to automatically peak and/or focus the antenna for the current location on the sky and with the current receiver, therefore it should not require any user input. However, by setting any of the optional arguments the user may partially or fully override the the calibration search and/or procedural steps as described below. The intent of the AutoOOF scan is to automatically run an Out of Focus holography scan for the current location on the sky and with the current receiver, therefore it should not require any user input. However, by setting any of the optional arguments the user may partially or fully override the the calibration search and/or procedural steps as described below. |
| Changed: | |
| < < | |
| > > | |
| Added: | |
| > > |
|
| Changed: | |
| < < | |
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.68 - 03 Jun 2008 - FrankGhigo) |
| Changed: | |
| < < |
AutoFocus/AutoPeak/AutoPeakFocus(source, location, frequency, flux, radius, balance, configure, beamName)
|
| > > |
AutoFocus/AutoPeak/AutoPeakFocus(source, location, frequency, flux, radius, balance, configure, beamName, gold)
|
| Added: | |
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.67 - 23 May 2008 - LarryMorgan) |
| Changed: | |
| < < |
RALongMap(location, hLength, vLength, vDelta, referenceOffset, referenceInterval, scanDuration, beamName, unidirectional, start, stop)
|
| > > |
RALongMapWithReference(location, hLength, vLength, vDelta, referenceOffset, referenceInterval, scanDuration, beamName, unidirectional, start, stop)
|
| Changed: | |
| < < | RALongMap?("CygA", |
| > > | RALongMapWithReference?("CygA", |
| <<O>> Difference Topic ScanTypes (r1.66 - 16 Apr 2008 - AmyShelton) |
| Changed: | |
| < < |
Peak("0137+3309", Offset("Encoder", "00:90:00", 0), Offset("Encoder, 0, "00:90:00"), 30, "1")
|
| > > |
Peak("0137+3309", Offset("Encoder", "00:90:00", 0), Offset("Encoder", 0, "00:90:00"), 30, "1")
|
| Changed: | |
| < < | The following example does a subreflector nod between beams 1 and 2 for 60 seconds, each nod or half-cycle lasts for three integrations where Rcvr26_40 was selected in the configuration: |
| > > | The following example does a subreflector nod between beams 1 and 2 for 60 seconds, each nod or half-cycle lasts for three integrations where Rcvr26_40 was selected in the configuration: |
| <<O>> Difference Topic ScanTypes (r1.65 - 20 Oct 2007 - MarkClark) |
| Changed: | |
| < < |
For two-beam receivers SubBeamNod causes the subreflector to tilt about the x axis between the two feeds at the given periodicity. The primary mirror is centered on the midpoint between the two beams. The beam selections are extracted from the scan's beamName, i.e., MR12 or MR34. The "first" beam ("1" or "3") performs the first integration. The periodicity is specified in seconds (float) per nod (half-cycle). A nod is limited to a minimum of 4.4 seconds. An example: Slew("3C48", beamName="MR12", submotion=SubNod(4.4826624)) Alternatively, one can specify the nod time in units of the primary backend's integration times (integer) by setting the periodicity units to integrations instead of the default seconds, e.g., Track("3C48", None, 60.0, beamName="MR12", submotion=SubNod(nodLength=3, nodUnit="integrations")) If the backend's actual integration time is obtainable then a warning is issued if the alignment between the integration times and the nod times shift over the duration of the scan by more than 10% of the nod time. A warning is issued in any case if the backend's actual integration time is not obtainable. Attempting to use integrations as the unit when the integration time cannot be obtained from the selected backend will cause a failure.
|
| > > |
For two-beam receivers SubBeamNod causes the subreflector to tilt about the x axis between the two feeds at the given periodicity. The primary mirror is centered on the midpoint between the two beams. The beam selections are extracted from the scan's beamName, i.e., MR12 or MR34. The "first" beam ("1" or "3") performs the first integration. The periodicity is specified in seconds (float) per nod (half-cycle). A nod is limited to a minimum of 4.4 seconds. An example: Track("3C48", None, 60.0, beamName="MR12", submotion=SubNod(4.4826624)) Alternatively, one can specify the nod time in units of the primary backend's integration times (integer) by setting the periodicity units to integrations instead of the default seconds, e.g., Track("3C48", None, 60.0, beamName="MR12", submotion=SubNod(nodLength=3, nodUnit="integrations")) If the backend's actual integration time is obtainable then a warning is issued if the alignment between the integration times and the nod times shift over the duration of the scan by more than 10% of the nod time. A warning is issued in any case if the backend's actual integration time is not obtainable. Attempting to use integrations as the unit when the integration time cannot be obtained from the selected backend will cause a failure. |
| <<O>> Difference Topic ScanTypes (r1.64 - 01 Oct 2007 - MarkClark) |
| Changed: | |
| < < | |
| <<O>> Difference Topic ScanTypes (r1.63 - 01 Oct 2007 - MarkClark) |
| Added: | |
| > > |
SubBeamNodSyntax:SubBeamNod(location, scanDuration, beamName, nodLength, nodUnit)
beamName, i.e., MR12 or MR34. The "first" beam ("1" or "3") performs the first integration. The periodicity is specified in seconds (float) per nod (half-cycle). A nod is limited to a minimum of 4.4 seconds. An example: Slew("3C48", beamName="MR12", submotion=SubNod(4.4826624)) Alternatively, one can specify the nod time in units of the primary backend's integration times (integer) by setting the periodicity units to integrations instead of the default seconds, e.g., Track("3C48", None, 60.0, beamName="MR12", submotion=SubNod(nodLength=3, nodUnit="integrations")) If the backend's actual integration time is obtainable then a warning is issued if the alignment between the integration times and the nod times shift over the duration of the scan by more than 10% of the nod time. A warning is issued in any case if the backend's actual integration time is not obtainable. Attempting to use integrations as the unit when the integration time cannot be obtained from the selected backend will cause a failure.
The following example does a subreflector nod between beams 1 and 2 for 60 seconds, each nod or half-cycle lasts
for three integrations where Rcvr26_40 was selected in the configuration:
SubBeamNod("1011-2610", 60.0, "MR12", nodLength=3, nodUnit="integrations")
Used with these GBT Standard Observing Modes: Position Switched (Dual Beam); Beam Switched
|
| <<O>> Difference Topic ScanTypes (r1.62 - 24 Sep 2007 - MarkClark) |
| Added: | |
| > > | |
| <<O>> Difference Topic ScanTypes (r1.61 - 12 Jul 2007 - MarkClark) |
| Added: | |
| > > | |
| <<O>> Difference Topic ScanTypes (r1.60 - 19 Mar 2007 - BrianMason) |
| Added: | |
| > > | WARNING: This procedure should be used with caution at high frequencies or in confused regions of the sky. Due to imprecisely repeatable scan-start overheads, the location of the OFF beam from one scan to the next is not guaranteed to be in a fixed place on the sky. Variations greater than an arcminute are not uncommon. |
| <<O>> Difference Topic ScanTypes (r1.59 - 12 Feb 2007 - MarkClark) |
| Changed: | |
| < < | This scan type performs a "Least Squares Frequency Switch" where a single scan is broken into 8 equal parts such that each subscan has a difference frequency (as described above). This routine was devised by Tim Robishaw and Carl Heiles to minimize the IF ripples in the bandpass. |
| > > | This scan type performs a "Least Squares Frequency Switch," where a single scan is broken into 8 equal parts, each observed at a unique frequency (as described above). This routine was devised by Tim Robishaw and Carl Heiles to minimize the IF ripples in the bandpass. |
| Changed: | |
| < < | (the data collector and switching signal generator) is set up for an |
| > > | (the data collector and switching signal generator) is set up for |
| <<O>> Difference Topic ScanTypes (r1.58 - 12 Feb 2007 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.57 - 25 Jan 2007 - MarkClark) |
| Added: | |
| > > | Note that to accomplish this ability, the spectrometer and LO1's switching signal states are defined differently, i.e., the spectrometer (the data collector and switching signal generator) is set up for an one scan with 8 equal integrations and 1 sig/ref period per integration. The LO1 (the frequency controller) is set up for an one scan, but with 8 sig/ref periods per scan. Then the delta-frequencies fed into the LO1 are doubles, i.e., f1, f1, f2, f2, f3, f3, ..., f8, f8, so each integration has two switching states which are equivalent. |
| Deleted: | |
| < < | -- MarkClark - 25 Jul 2006 |
| <<O>> Difference Topic ScanTypes (r1.56 - 14 Dec 2006 - MarkClark) |
| Deleted: | |
| < < | This scan type wo |
| <<O>> Difference Topic ScanTypes (r1.55 - 21 Nov 2006 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.54 - 11 Oct 2006 - FrankGhigo) |
| Added: | |
| > > | |
| <<O>> Difference Topic ScanTypes (r1.53 - 06 Oct 2006 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.52 - 25 Jul 2006 - MarkClark) |
| Changed: | |
| < < | SOM: Focus Peak Corrections |
| > > | Used with these GBT Standard Observing Modes: Focus Peak Corrections |
| Changed: | |
| < < | SOM: |
| > > | Used with these GBT Standard Observing Modes: |
| Changed: | |
| < < | SOM: OTF Map; Continuum Map |
| > > | Used with these GBT Standard Observing Modes: OTF Map; Continuum Map |
| Changed: | |
| < < | SOM: OTF Map; Continuum Map |
| > > | Used with these GBT Standard Observing Modes: OTF Map; Continuum Map |
| Changed: | |
| < < | SOM: Corrections |
| > > | Used with these GBT Standard Observing Modes: Corrections |
| Changed: | |
| < < | SOM: Z17; Spider |
| > > | Used with these GBT Standard Observing Modes: Z17; Spider |
| Changed: | |
| < < | SOM: Position Switched (Dual Beam); Beam Switched |
| > > | Used with these GBT Standard Observing Modes: Position Switched (Dual Beam); Beam Switched |
| Changed: | |
| < < | SOM: Position Switched (Single Beam) |
| > > | Used with these GBT Standard Observing Modes: Position Switched (Single Beam) |
| Changed: | |
| < < | SOM: Position Switched (Single Beam) |
| > > | Used with these GBT Standard Observing Modes: Position Switched (Single Beam) |
| Changed: | |
| < < | SOM: Position Switched (Single Beam) |
| > > | Used with these GBT Standard Observing Modes: Position Switched (Single Beam) |
| Changed: | |
| < < | SOM: Position Switched (Single Beam) |
| > > | Used with these GBT Standard Observing Modes: Position Switched (Single Beam) |
| Changed: | |
| < < | SOM: Pointing Corrections |
| > > | Used with these GBT Standard Observing Modes: Pointing Corrections |
| Changed: | |
| < < | SOM: Point Map |
| > > | Used with these GBT Standard Observing Modes: Point Map |
| Changed: | |
| < < | SOM: Point Map |
| > > | Used with these GBT Standard Observing Modes: Point Map |
| Changed: | |
| < < | SOM: OTF Map; Continuum Map |
| > > | Used with these GBT Standard Observing Modes: OTF Map; Continuum Map |
| Changed: | |
| < < | SOM: OTF Map; Continuum Map |
| > > | Used with these GBT Standard Observing Modes: OTF Map; Continuum Map |
| Changed: | |
| < < | SOM: LSFS; Z17 |
| > > | Used with these GBT Standard Observing Modes: LSFS; Z17 |
| Changed: | |
| < < | SOM: Tipping Scan |
| > > | Used with these GBT Standard Observing Modes: Tipping Scan |
| Changed: | |
| < < | SOM: Total Power Track; Frequency Switched Track; VLBI; Pulsar; Radar |
| > > | Used with these GBT Standard Observing Modes: Total Power Track; Frequency Switched Track; VLBI; Pulsar; Radar |
| Changed: | |
| < < | SOM: LSFS; Spider |
| > > | Used with these GBT Standard Observing Modes: LSFS; Spider |
| Changed: | |
| < < | -- KarenONeil - 17 May 2006 |
| > > | -- MarkClark - 25 Jul 2006 |
| <<O>> Difference Topic ScanTypes (r1.51 - 28 Jun 2006 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.50 - 18 May 2006 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.49 - 17 May 2006 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | This command scans in the Dec or latitude-like direction, map columns are offset in RA |
| > > | This command scans in the Dec or latitude-like direction, and steps in RA |
| Changed: | |
| < < | Note that the "Location" may be in a different coordinate system than the "Offsets". |
| > > | Note that the "Location" may be in a different coordinate system than the lengths. |
| Changed: | |
| < < | A Declination/Latitude map with reference source, or DecLatMapWithReference, does a raster scan centered on a specific location on the sky and periodically moves to a reference location on the sky. Scaning is done in the declination, latitude, or elevation coordinate depending on the desired coordinate mode. This procedure does allows the user to periodically move to a reference offset on the sky, please see DecLatMap if no reference point is required. The starting point of the map is defined as (-hLength/2, -vLength/2). |
| > > | A Declination/Latitude map with reference source, or DecLatMapWithReference, does a raster scan centered on a specific location on the sky and periodically moves to a reference location on the sky. Scaning is done in the declination, latitude, or elevation coordinate depending on the desired coordinate mode. This procedure does allows the user to periodically move to a reference position on the sky, please see DecLatMap if no reference point is required. The starting point of the map is defined as (-hLength/2, -vLength/2). |
| Changed: | |
| < < |
Focus(location, start, offset, scanDuration, beamName)
|
| > > |
Focus(location, start, focusLength, scanDuration, beamName)
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | The Focus procedure sweeps the subreflector or prime focus (depending on the receiver in use) through the axis aligned with the beam. Its primary use is to determine focus offsets for use in subsequent scans. Note that the offset and scanDuration should be overridden as a unit since together they determine the rate. |
| > > | The Focus procedure sweeps the subreflector or prime focus (depending on the receiver in use) through the axis aligned with the beam. Its primary use is to determine focus positions for use in subsequent scans. Note that the FocusLength? and scanDuration should be overridden as a unit since together they determine the rate. |
| Changed: | |
| < < | |
| > > | |
| Changed: | |
| < < |
OffOn(location, offset, scanDuration, beamName)
|
| > > |
OffOn(location, referenceOffset, scanDuration, beamName)
|
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > |
|
| Changed: | |
| < < | The OffOn scan performs two subscans. The first subscan is at an offset to the source used in the second subscan and the second subscan is on source. |
| > > | The OffOn scan performs two subscans. The first subscan is offset from the location, used in the second scan by the referenceOffset and subscan is on source. |
| Changed: | |
| < < | The following example does an OffOn scan with offsets of 1 degree in width and height and a 60 second subscan duration, using beam 1: |
| > > | The following example does an OffOn scan with reference offsets of 1 degree in width and height and a 60 second subscan duration, using beam 1: |
| Changed: | |
| < < |
OnOff(location, offset, scanDuration, beamName)
|
| > > |
OnOff(location, referenceOffset, scanDuration, beamName)
|
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > |
|
| Changed: | |
| < < | The following example does an OnOff scan with offsets of 1 degree in width and height and a 60 second subscan duration, using beam 1: |
| > > | The following example does an OnOff scan with reference offsets of 1 degree in width and height and a 60 second subscan duration, using beam 1: |
| Changed: | |
| < < |
Peak(location, hOffset, vOffset, scanDuration, beamName)
|
| > > |
Peak(location, hLength, vLength, scanDuration, beamName)
|
| Changed: | |
| < < | |
| > > | |
| Changed: | |
| < < | The Peak scan type sweeps through the specified sky location in the four cardinal directions. Its primary use is to determine pointing offsets for use in subsequent scans Note that the offsets and scanDuration should be overridden as a unit since together they determine the rate. |
| > > | The Peak scan type sweeps through the specified sky location in the four cardinal directions. Its primary use is to determine pointing corrections for use in subsequent scans Note that the hLength/vLength and scanDuration should be overridden as a unit since together they determine the rate. |
| Changed: | |
| < < | The following example does a peak in encoder coordinates with 90 minute offsets and a 30 second subscan duration using beam 1. |
| > > | The following example does a peak in encoder coordinates with 90 minute lengths and a 30 second subscan duration using beam 1. |
| Changed: | |
| < < | |
| > > | |
| Changed: | |
| < < |
Tip(location, offset, scanDuration, beamName, startTime, stopTime)
|
| > > |
Tip(location, endOffset, scanDuration, beamName, startTime, stopTime)
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
Track(location, offset, scanDuration, beamName, startTime, stopTime)
|
| > > |
Track(location, endOffset, scanDuration, beamName, startTime, stopTime)
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | |
| > > | -- KarenONeil - 17 May 2006 |
| <<O>> Difference Topic ScanTypes (r1.48 - 07 Apr 2006 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.47 - 07 Apr 2006 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.46 - 29 Mar 2006 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
Slew(location, beamName)
|
| > > |
Slew(location, offset, beamName)
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
Slew moves the telescope to point to a specified location on the sky. If you would like to Slew to an offset from a location on the sky, simply add a Location to an Offset, e.g. Slew(Location("J2000", "01:37:41.30", "+33:09:35.4") + Offset("J2000", 2.0, 0.0)) or you can do the addition outside of Slew by writing something like position = Location("J2000", "01:37:41.30", "+33:09:35.4") + Offset("J2000", 2.0, 0.0) and then Slew(position). Or with a catalog position = catalog['3C48']['location'] + Offset("J2000", 2.0, 0.0).
|
| > > |
Slew moves the telescope beam to point to a specified location on the sky.
|
| Changed: | |
| < < | Slew("3C48", "C") |
| > > |
Catalog("fluxcal")
Slew("3C48", beamName="C")
Note that Slew() with no arguments is basically a NOP, i.e., it slews to the current location (but in J2000):
Slew() # ??Though one could change beams at that position: Slew(beamName="2") |
| Added: | |
| > > | |
| Changed: | |
| < < | --> |
| > > | |
| Added: | |
| > > | --> |
| Changed: | |
| < < | Scan timing must be specified by either a scanDuration, a stopTime, or a startTime plus scanDuration. |
| > > | Scan timing must be specified by either a scanDuration, a stopTime, a startTime plus stopTime, or a startTime plus scanDuration. |
| Changed: | |
| < < | Scan timing must be specified by either a scanDuration, a stopTime, or a startTime plus scanDuration. |
| > > | Scan timing must be specified by either a scanDuration, a stopTime, a startTime plus stopTime, or a startTime plus scanDuration. |
| <<O>> Difference Topic ScanTypes (r1.45 - 25 Mar 2006 - BrianMason) |
| Changed: | |
| < < | Brian, need meatier description here. |
| > > | The area of the sky covered will be circular, with a diameter equal to twice the specified map_radius. For map radii of a few arcminutes, a radial_osc_period of 60 sec or longer is recommended; a scanDuration of 20 radial_osc_period's will result in an approximately closed pattern. For beamsizes of 20 arcsec (fwhm) or so, the circular area mappped will be fully sampled if the map radius is less than 6'. It is not an especially useful observing mode for general-purpose single-beam mapping, since the largest "hole" in the map is approximately 0.3 x map_radius. However it is useful for focal-plane arrays. |
| Changed: | |
| < < | Daisy("3C123", 5, 30, 0, 0, 150) |
| > > | Daisy(location="3C123", map_radius=5, radial_osc_period=60, radial_phase=0, rotation_phase=0, scanDuration=1200) |
| <<O>> Difference Topic ScanTypes (r1.44 - 23 Mar 2006 - MarkClark) |
| Changed: | |
| < < | |
| > > | |
| Changed: | |
| < < | |
| > > | |
| Changed: | |
| < < | |
| > > | |
| <<O>> Difference Topic ScanTypes (r1.43 - 21 Mar 2006 - MarkClark) |
| Changed: | |
| < < | This scan type is used for polarization studies, but could be used for other observing schemes, |
| > > | This scan type wo This scan type is used for polarization studies, but could be used for other observing schemes. It only works with the Spectrometer backend. |
| Changed: | |
| < < |
Tip(location, offset, scanDuration, beamName)
|
| > > |
Tip(location, offset, scanDuration, beamName, startTime, stopTime)
|
| Added: | |
| > > |
|
| Added: | |
| > > | Scan timing must be specified by either a scanDuration, a stopTime, or a startTime plus scanDuration. |
| Added: | |
| > > | Scan timing must be specified by either a scanDuration, a stopTime, or a startTime plus scanDuration. |
| <<O>> Difference Topic ScanTypes (r1.42 - 17 Mar 2006 - MarkClark) |
| Changed: | |
| < < | This scan type performs a "Least Squares Frequency Switch" where a single scan is broken into 8 equal parts such that each subscan has a difference frquency (as described above). This routine was devised by Tim Robishaw and Carl Heiles to minimize the IF ripples in the bandpass. |
| > > | This scan type performs a "Least Squares Frequency Switch" where a single scan is broken into 8 equal parts such that each subscan has a difference frequency (as described above). This routine was devised by Tim Robishaw and Carl Heiles to minimize the IF ripples in the bandpass. |
| <<O>> Difference Topic ScanTypes (r1.41 - 17 Mar 2006 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | This scan type performs a "Least Squares Frequency Switch" where a single subscan is broken into 8 equal parts such that |
| > > | This scan type performs a "Least Squares Frequency Switch" where a single scan is broken into 8 equal parts such that each subscan has a difference frquency (as described above). This routine was devised by Tim Robishaw and Carl Heiles to minimize the IF ripples in the bandpass. |
| Changed: | |
| < < | This scan type is used for polarization studies. |
| > > | This scan type is used for polarization studies, but could be used for other observing schemes, The following example generates a subscan at 1258+6126: |
| Deleted: | |
| < < | The following example generates a subscan at 1258+6126 ... |
| Changed: | |
| < < | LSFS("1258+6126", 12.5/512.0, 80.0) |
| > > | LSFS("1258+6126",0.0244,80) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | Spider executes the specified number of symmetrical slices or cross subscans of length scanDuration through the specified location. Each slice is of length 2*offset. The argument offset also specifies the angle of the initial slice. The user may specify unidirectional or bidirectional subscans of length calDuration and when to run calibration subscans relative to each slice, i.e., at "begin", "end", or "both". |
| > > | Spider executes the specified number of slices of length scanDuration through the specified location. Each slice is of length 2*offset. The argument offset also specifies the angle of the initial slice. The user may specify unidirectional or bidirectional subscans of length calDuration and when to run calibration subscans relative to each slice, i.e., at "begin", "end", or "both". |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | Z17 executes two circles of point subscans around location at 45 degree intervals. The first circle with a radius of offset and the second circle at a radius of sqrt(2)*offset. The initial subscan is at the angle specified by the offset. After circling twice, the procedure executes a subscan on location. The entire set of 17 subscans each of length scanDuration, is sandwiched between two cal subscans of lengths calDuration which consist of equal parts calibration noise signal on and off. |
| > > | Z17 executes two circles of point subscans around location at 45 degree intervals. The first circle with a radius of offset and the second circle at a radius of sqrt(2)*offset. The initial subscan is at the angle specified by the offset. After circling twice, the procedure executes a subscan on location. The entire set of 17 subscans each of length scanDuration, is sandwiched between two cal subscans of lengths calDuration which consist of equal parts calibration noise signal on and off. |
| <<O>> Difference Topic ScanTypes (r1.40 - 16 Mar 2006 - MarkClark) |
| Added: | |
| > > |
DaisySyntax:Daisy(location, map_radius, radial_osc_period, radial_phase, rotation_phase, scanDuration, beamName, cos_v, coordMode, calc_dt)
Catalog("fluxcal")
Daisy("3C123", 5, 30, 0, 0, 150)
SOM:
|
| <<O>> Difference Topic ScanTypes (r1.39 - 15 Mar 2006 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.38 - 15 Mar 2006 - MarkClark) |
| Added: | |
| > > | This scan type performs a "Least Squares Frequency Switch" where a single subscan is broken into 8 equal parts such that |
| <<O>> Difference Topic ScanTypes (r1.37 - 09 Mar 2006 - MarkClark) |
| Added: | |
| > > |
LSFSSyntax:LSFS(location, deltaf, scanDuration, beamName)
Catalog()
LSFS("1258+6126", 12.5/512.0, 80.0)
SOM: Z17; Spider
|
| Added: | |
| > > |
SpiderSyntax:Spider(location, offset, scanDuration, slices, beamName, unidirectional, cals, calDuration)
Catalog()
Spider("1258+6126", Offset("AzEl", "00:40:00", "00:00:00"), 30.0)
SOM: LSFS; Z17
|
| Added: | |
| > > |
Z17Syntax:Z17(location, offset, scanDuration, beamName, calDuration)
Catalog()
Z17("1258+6126", Offset("AzEl", "00:09:00", "00:00:00", cosv=True), 60.0)
SOM: LSFS; Spider |
| <<O>> Difference Topic ScanTypes (r1.36 - 15 Feb 2006 - MarkClark) |
| Deleted: | |
| < < | |
| Changed: | |
| < < |
AutoFocus/Peak/PeakFocus(source, frequency, flux, radius, balance, abort)
|
| > > |
AutoFocus/AutoPeak/AutoPeakFocus(source, location, frequency, flux, radius, balance, configure, beamName)
|
| Changed: | |
| < < |
The intent of this scan is to automatically peak and/or focus the antenna for current location on the sky and with the current receiver, therefore it should not require any user input, however, if desired, any of its six defaulted parameters may be overridden.
Parameter Info:
|
| > > | The intent of this scan is to automatically peak and/or focus the antenna for the current location on the sky and with the current receiver, therefore it should not require any user input. However, by setting any of the optional arguments the user may partially or fully override the the calibration search and/or procedural steps as described below. |
| Changed: | |
| < < | The procedure determines the current beam location and receiver, configures the telescope using a standard continuum configuration for the current receiver, selects a nearby calibrator, balances the input levels, and runs the appropriate scan as described below. Note that since the scan is self-configuring, one must re-configure for regular programming. One may examine the candidate sources in Condon's pointing catalog by running calfind directly. |
| > > |
The sequence of events in full automatic mode, i.e, with no arguments are:
|
| Changed: | |
| < < | SOM: Focus Peak Corrections |
| > > | SOM: Focus Peak Corrections |
| Changed: | |
| < < |
FocusIt is required that you slew to your source before you attempt to focus. If you try to focus without first being on source, the telescope will try to focus at the last location stored in the antenna, which is probably not on your source. You will end up with LFCs that are extremely unreasonable and you will have little or no apparent signal in your data. |
| > > |
Focus |
| Changed: | |
| < < |
Focus(location, offset, scanDuration, beamName)
|
| > > |
Focus(location, start, offset, scanDuration, beamName)
|
| Added: | |
| > > | The only required parameter is location. |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | The Focus procedure sweeps the subreflector or prime focus (depending on the receiver in use) through the axis aligned with the beam. Its primary use is to determine pointing offsets for use in subsequent procedures. |
| > > | The Focus procedure sweeps the subreflector or prime focus (depending on the receiver in use) through the axis aligned with the beam. Its primary use is to determine focus offsets for use in subsequent scans. Note that the offset and scanDuration should be overridden as a unit since together they determine the rate. |
| Changed: | |
| < < | The following example assumes that you have already slewed to your source. A focus subreflector is performed from -200 to +200mm at 400mm/min using beam 1: |
| > > | Important: Because of the addition of the location keyword, Focus will not be backwards compatible. |
| Added: | |
| > > |
In the following example a focus subreflector is performed from -200 to +200mm at 400mm/min using beam 1:
Focus("0137+3309", -200.0, 400.0, 60.0, "1")
|
| Changed: | |
| < < |
Focus(-200.0, 400.0, 60.0, "1")
|
| > > |
Focus("0137+3309")
|
| Changed: | |
| < < | SOM: Focus Corrections |
| > > | SOM: Corrections |
| Added: | |
| > > | The only required parameter is location. |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | The Peak scan type sweeps through the specified sky location in the four cardinal directions. Its primary use is to determine pointing offsets for use in subsequent procedures. |
| > > | The Peak scan type sweeps through the specified sky location in the four cardinal directions. Its primary use is to determine pointing offsets for use in subsequent scans Note that the offsets and scanDuration should be overridden as a unit since together they determine the rate. |
| Changed: | |
| < < | SOM: Pointing Corrections |
| > > | or with the defaults. |
| Added: | |
| > > |
Peak("0137+3309")
SOM: Pointing Corrections |
| <<O>> Difference Topic ScanTypes (r1.35 - 19 Sep 2005 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > | One may examine the candidate sources in Condon's pointing catalog by running calfind directly. |
| <<O>> Difference Topic ScanTypes (r1.34 - 19 Sep 2005 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.33 - 14 Sep 2005 - AmyShelton) |
| Changed: | |
| < < | Please note that the syntax for all Scan Types is case-sensitive. |
| > > | Please note that the syntax for all Scan Types is case-sensitive. |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ScanTypes (r1.32 - 13 Sep 2005 - AmyShelton) |
| Added: | |
| > > | Please note that the syntax for all Scan Types is case-sensitive. |
| <<O>> Difference Topic ScanTypes (r1.31 - 16 Aug 2005 - MarkClark) |
| Changed: | |
| < < | A Scan, formerly referred to as an observing procedure, is a pattern of antenna motio |