Requirements: Collection Support: VLA Pulsar Observation
Pulsar file ingestion and metadata extraction will proceed similarly to an EVLA SDM ingestion with possible additional (science, ancillary?) products, identified in a metadata.json file.
Binned Imaging Observations
In binning mode there are no additional products. The only science product is the execution block as defined by the SDM. The SDM will contain an additional table, Pulsar.xml which will give the metadata for the scans using binning mode. Scan information is retrieved using a standard SDM approach: Main.xml contains scans and a pointer to a Config Description which contains a pointer to a Data Description which may contain a pointer to an entry in the Pulsar table. If there is no pointer to the Pulsar table in the Data Description, binning mode was not used for that scan.
<row>
<dataDescriptionId>DataDescription_15</dataDescriptionId>
<polOrHoloId>Polarization_0</polOrHoloId>
<spectralWindowId>SpectralWindow_15</spectralWindowId>
</row>
<row>
<dataDescriptionId>DataDescription_16</dataDescriptionId>
<polOrHoloId>Polarization_0</polOrHoloId>
<pulsarId>Pulsar_0</pulsarId> <--- indicates binning mode for the scan
<spectralWindowId>SpectralWindow_0</spectralWindowId>
</row>
Phased-array Observations
The original ticket stated that there should be 1 pulsar file per observation. The matching should occur by a substring of the file name. Looking in /lustre/aoc/sciops/pdemorest/18A-210 at eb 18A-210_sb35401562_1_1.58271.256401238425, I see 84 matching files.
So the issue of mapping observation to pulsar file is still not decided. If I have a specific example I can use that.