2. ODS Use Cases
Below are descriptions on how ODS reports some of the common use cases for our facilities
2.1. General observation
Pending
2.2. Subarrays
Pending
2.3. Non-sidereal sources
2.3.1. Target position and pointing
In astronomical observations, the location of a celestial object is primarily defined using Right Ascension (RA) and Declination (Dec) coordinates. These are represented in ODS data by the src_ra_j2000_deg and src_dec_j2000_deg fields, indicating the position in Degrees for the J2000 epoch.
2.3.2. Sidereal targets
Sidereal targets are objects like stars and galaxies whose apparent positions in the sky remain essentially constant over the duration of an observation. For these targets, the initial RA and Dec coordinates are sufficient, and no updates are needed during the observation interval.
2.3.3. Slow-moving non-sidereal targets
Non-sidereal targets are objects that show noticeable movement across the sky. This motion is often referred to as proper motion. For these targets, multiple ODS data entries, or Mitigation Requests (MRs), may be needed to account for their changing positions. The update cadence of these MRs depends on how significantly the RA-Dec coordinates change relative to the size of the telescope and downlink beams.
As a general guideline, position updates for moving targets should not exceed the inverse of the proper motion (1/pm), where pm is expressed in Degrees per Second (dps). This ensures that updates are frequent enough to track the object accurately without pushing too many MRs to the API at once.
For many Solar System bodies, such as objects in the asteroid belt or the Voyager spacecrafts, the proper motion is relatively slow, often in the order of tens of Arcseconds per Hour, or about one micro-Degree per Second (0.000001 dps). At these slow rates, position updates are generally unnecessary and can be kept as a single RA-Dec value in the MR.
2.3.4. Fast-moving non-sidereal targets
Some observation techniques involve rapidly scanning the sky, which necessitates more frequent position updates. Examples include:
1. Tipping scans, which involve quickly moving the telescope to observe different points in the sky to measure atmospheric opacity; 2. Drift scanning, where the beam of the antenna sweeps across the sky due to Earth’s rotation (slewing or not the antenna);
For these rapid scanning methods, the observation needs to be divided into multiple MRs. A few position updates per minute are typically sufficient to maintain accurate pointing for mitigation.
2.3.5. On-Off source observing strategy
On-Off source calibration involves the telescope pointing at a nearby, source-free patch of sky to measure the background flux level. “Off” positions can be several degrees away from the target, such as during Galactic Center observations or when dealing with L-band beam shifts. The general guideline is to report these On-Off positions in specific MRs, unless they are very close (e.g. fraction of a degree at high frequency).
2.3.6. Atmospheric refraction
The ODS system currently disregards atmospheric refraction for pointing. This approach is justified by the hypothesis that any pointing error caused by refraction is much smaller than the telescope’s beamwidth and/or the region of the sky being addressed by mitigation efforts.
2.4. Multiple mitigation requests (MR’s) handling
Pending
2.5. Edge cases
Pending