 Requirements: Collection Support: VLA Pulsar Observation
JIRA Ticket:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Pulsar file ingestion and metadata extraction will proceed similarly to an EVLA SDM ingestion with possible additional (science, ancillary?) products. Manifest ingestion will be used with a manifest.json file to identify products and , identified in a metadata.json file to identify additional metadata to be extracted from the SDM or additional files.
Binned Imaging Observations
...
Phased-array Observations
Examples: /lustre/aoc/sciops/pdemores/
.cf calibration files
.ar pulsar data files
File set: 18A-210_sb35398245_1_1.58270.41125583333
Associated files:
<file set>.scan_id.subscan_id.IF_name.Index_within_subscan/IF_[.ar | .cf]
18A-210_sb35395090_1_1.58251.80414998843.14.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.14.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.15.1.AC_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.15.1.AC_0002.ar
18A-210_sb35395090_1_1.58251.80414998843.15.1.AC_0003.ar
18A-210_sb35395090_1_1.58251.80414998843.15.1.AC_0004.ar
18A-210_sb35395090_1_1.58251.80414998843.15.1.BD_0001.ar
18A-210/18A-210_sb35395090_1_1.58251.80414998843.15.1.BD_0002.ar
18A-210/18A-210_sb35395090_1_1.58251.80414998843.15.1.BD_0003.ar
18A-210_sb35395090_1_1.58251.80414998843.15.1.BD_0004.ar
18A-210_sb35395090_1_1.58251.80414998843.16.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.16.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.27.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.27.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.28.1.AC_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.AC_0002.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.AC_0003.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.AC_0004.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.BD_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.BD_0002.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.BD_0003.ar
18A-210_sb35395090_1_1.58251.80414998843.28.1.BD_0004.ar
18A-210_sb35395090_1_1.58251.80414998843.29.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.29.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.30.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.30.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.3.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.3.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.41.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.41.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.42.1.AC_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.42.1.BD_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.43.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.43.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.54.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.54.1.BD_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.55.1.AC_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.55.1.BD_0001.ar
18A-210_sb35395090_1_1.58251.80414998843.56.1.AC_0001.cf
18A-210_sb35395090_1_1.58251.80414998843.56.1.BD_0001.cf
Metadata
For the PSRFITS files:
| Observing Mode | hdu['PRIMARY'].header['OBS_MODE'] |
| Number of bins | hdu['SUBINT'].header['NBIN'] |
| Time resolution | |
| Number of channels | hdu['SUBINT'].header['NCHAN'] |
| Number of polarization products | hdu['SUBINT'].header['NPOL'] |
| Period | |
| Dispersion Measure | hdu['SUBINT'].header['DM'] |
Notes
It is possible for an observation to use 'mixed-modes'. Some scans could use binning mode and other scans could use phased-array mode.
Summary
For binned mode, the pulsar metadata is part of the SDM and can be handled with an extension of the standard SDM ingestion with additional fields in the database for the metadata.
For phased-array mode, the pulsar metadata is contained in the .ar and .cf PSRFITS files. In this case, it might be technically more feasible to extract the metadata from the PSRFITS files and place them in a metadata.json file that represents metadata per scan/subscan (IF?).
The PSRFITS files represent ancillary products of the execution block science product. They do, however, provide additional metadata for the execution block at the individual scan level.