9: Dynamic Spectrum: Conceptual Model
10: Dynamic Spectrum: Logical Model
A PSRFITS file is generated for each PST output sub-integration (every
10s).
The PSRFITS files will contain the following:
-
Metadata: The Dynamic Spectrum Metadata shall be stored in the PSRFITS
data file as keywords [AD5].
-
Data cube metadata: Diagnostic and heuristic metadata
-
Data cube: Dynamic spectra
The PSRFITS file may also include optional extensions (e.g. digitiser
statistics) as per the standard [AD5].
File format: PSRFITS [AD5]
The PSRFITS version number is not specified in this ICD because it is
defined in the header of the file.
5.3.1.4.3. Flow
Through data types
The raw beam-formed voltage data are defined as the first
moments of the electric field, with no temporal or spectral averaging,
but optional re-quantisation (e.g. from 8 bits per sample to 2 bits per
sample).
A raw data file is generated for each PST output sub-integration (every
10s).
The raw data files will contain the following:
-
Metadata: Flow Through metadata (Metadata shall be stored in the
header of the data file (TBD-009 ))
-
Data cube: raw beam-formed voltages
File format: TBD-010
Failure of the communication link or the receipt of incorrectly
formatted data results in an alarm being generated.
This section shows the variability than can be expected and any
constraints on specific use cases of the interface or particular aspects
of the interface.
Note that parameter values for modes shown in this section are
expected or typical values and are provided for information only. This
interface does not constrain parameter values unless explicitly stated
as a constraint. Actual parameter values will be chosen by Telescope
Manager (for each scheduling block and its scans) according to the
requirements of the observation and any constraints imposed by
components of the telescope [AD6].
Since the beams are independent of each other, a combination of the
different observing modes can be used simultaneously. Only one
(1) observing mode can be used for a particular Pulsar Timing beam.
This also implies that each PST beam can be processed completely
independent of the others, and hence all 16 PST beams do not need to be
processed by SDP on the same compute node.
5.3.1.6.1.
Pulsar Timing Mode Variability
The following Pulsar Timing modes are supported:
-
Ordinary and millisecond pulsars (MSPs)
-
Pulsar Timing Array (PTA)
These Pulsar Timing modes generate the same data, but with different
parameter configurations, see Table 12.
The pulsar timing data cube will have the following axes
(SDP_REQ_INT-324):
-
pulse profile bins
-
frequency channels
-
Sub-integrations
-
polarisation parameters
Table 15 provides the range of parameter values for the 2 Pulsar Timing
observing modes as well as a worst case scenario.
15: Pulsar Timing Parameters