Open Questions
We need to clearly define the parameters of a Field Source and
address the following questions:
- Should we adopt the ALMA model?
- Should the Field Source parameters vary with Facility? Or Capability?
- Should file import/export format include all fields? Be fixed?
ALMA OT
From ALMA's OT User Manual (March 2022) the current file import
format is:
Name, RA|Galactic Long (Degs), Dec|Galactic Lat (Degs), PMRA(mas/yr), PMDec(mas/yr),
vel(km/s), Ref frame, Doppler type, peak cont flux(mJy), peak line flux(mJy), cont pol(%),
line pol(%), line width(km/s), cont circular pol (%), line circular pol (%)
-- This signals end of the header
ngc253, 00:47:33.134, -25:17:19.68, 0.0, 0.0, 258.6, lsrk, RADIO, 200, 1000, 2, 0, 1500, 0, 0
ngc1068, 02:42:40.771, -00:00:47.84, 0.0, 0.0, 1142.0, topo, OPTICAL, 1100.0, 30, 0, 0, 20, 0, 0
In the ALMA OT Cycle 9 UI the following fields exist but are not in the file import:
System (e.g., ICRS)
Parallax
Target Type (e.g., single pointing or 1 rectangular field)
For the TTAT we currently have:
Name, Coordinate System, Right Ascension, Declination, RA Uncertainty, Declination Uncertainty, Field Of View Shape, FOV in RA, FOV in Dec, Radial Velocity, Velocity Reference Frame, Doppler Type, Parallax, Proper Motion in RA, Proper Motion in Dec, Peak Continuum Flux Density
G32.0+1.0, IRCS, 281.54463757, -0.37327736, 0, 0, rectangle, 0.001, 0.001, 10.0, LRSK, Radio, 0.0, 0.0, 0.0, 1.0
G35.0+1.0, IRCS, 282.91234293, 2.29646173, 0, 0, rectangle, 0.001, 0.001, 10.0, LRSK, Radio, 0.0, 0.0, 0.0, 1.0
Use Cases
From the Use Case document (March 7, 2023) it appears that the Field Source parameters need to depend on the Capability. For example, the Pulsar Use Case notes "The user may optionally specify an estimate of the mean flux density, period, duty cycle, or dispersion measure; otherwise these would take on default or null values." So ideally the Field Source parameters would be a function of Capability and so the file import format would vary. We would therefore want this to be configurable via Solicitations.
N.B., Upon discussion we had already concluded that Field Sources had to be a function of Capability and need to be configurable. See the Algorithms document for a path forward on how this will work.