Low TMC configure 3.0

Example JSON.

{
    "interface": "https://schema.skao.int/ska-low-tmc-configure/3.0",
    "transaction_id": "txn-....-00001",
    "mccs": {
        "stations": [{
            "station_id": 1
        }, {
            "station_id": 2
        }],
        "subarray_beams": [{
            "subarray_beam_id": 1,
            "station_ids": [1, 2],
            "update_rate": 0.0,
            "channels": [
                [0, 8, 1, 1],
                [8, 8, 2, 1],
                [24, 16, 2, 1]
            ],
            "antenna_weights": [1.0, 1.0, 1.0],
            "phase_centre": [0.0, 0.0],
            "target": {
                "reference_frame": "HORIZON",
                "target_name": "DriftScan",
                "az": 180.0,
                "el": 45.0
            }
        }]
    },
    "sdp": {
        "interface": "https://schema.skao.int/ska-sdp-configure/0.4",
        "scan_type": "target:a"
    },
    "csp": {
        "interface": "https://schema.skao.int/ska-low-csp-configure/2.0",
        "subarray": {
            "subarray_name": "science period 23"
        },
        "common": {
            "config_id": "sbi-mvp01-20200325-00001-science_A",
            "subarray_id": 1
        },
        "lowcbf": {
            "stations": {
                "stns": [
                    [1, 0],
                    [2, 0],
                    [3, 0],
                    [4, 0]
                ],
                "stn_beams": [{
                    "beam_id": 1,
                    "freq_ids": [64, 65, 66, 67, 68, 69, 70, 71],
                    "boresight_dly_poly": "url"
                }]
            },
            "timing_beams": {
                "beams": [{
                    "pst_beam_id": 13,
                    "stn_beam_id": 1,
                    "offset_dly_poly": "url",
                    "stn_weights": [0.9, 1.0, 1.0, 0.9],
                    "jones": "url",
                    "rfi_enable": [true, true, true],
                    "rfi_static_chans": [1, 206, 997],
                    "rfi_dynamic_chans": [242, 1342],
                    "rfi_weighted": 0.87
                }]
            }
        }
    },
    "tmc": {
        "scan_duration": 10.0
    }
}

https://schema.skao.int/ska-low-tmc-configure/3.0
type	object
properties
interface	URI of JSON schema applicable to this JSON payload.
	type	string
transaction_id	A transaction id specific to the command
	type	string
	default	null
mccs	MCCS configuration specification.
	type	object
	properties
	stations	IDs of the MCCS stations to configure. Maximum array size = 512, the maximum number of MCCS stations.
		type	array
		default	null
		items	type	object
			properties
			station_id	MCCS Station ID. Each ID must be between 1 and 512.
				type	integer
			additionalProperties	False
	subarray_beams	MCCS sub-array beam configuration.
		type	array
		items	type	object
			properties
			subarray_beam_id	ID of MCCS sub-array beam to configure. ID must be an integer between 1 and 48.
				type	integer
			update_rate	Update rate for pointing information. Value must be 0.0 or greater. TODO: clarify whether this is specified as a frequency or as a cadence, plus units.
				type	number
			station_ids	IDs of MCCS stations within this sub-array beamto configure. Array size must be less than 512, the maximum number of MCCS stations. Each item in the list must be an integer between 1 and 512.
				type	array
				default	null
				items	type	integer
			channels	Channel block configurations. Each item in the list is a channel block configuration, each specified as a list of 4 numbers as follows: [start channel, number of channels, beam index, sub-station index] Constraints are: 0 < start channel < 376 start channel must be a multiple of 8 8 < number of channels < 48 1 < beam index < 48 1 < sub-station index < 8
				type	array
				default	null
				items	type	array
					items	type	integer
			antenna_weights	Antenna weights. Maximum array size = 512 (=256 antennas x2 pols per sub-array beam). Antennas signals can be weighted to modify the station beam, varying from 0.0 for full exclusion to potentially 256.0 for an antenna contribution compensated for the number of antennas in the beam. This value is an amplitude multiplier added to that antenna signal before adding into the sum. Weights apply to all channels assigned to a beam.
				type	array
				default	null
				items	type	number
			phase_centre	Phase centre offset for the station beam, in metres. The reference position for station phase must be modified to reflect antenna weighting and their contribution to the station beam. This offset can be can considered the desired centre of mass for the station. Constraints: array size = 2 -20 < phase centre value < 20
				type	array
				default	null
				items	type	number
			target	Target position for the sub-array beam. Only drift scan targets are currently implemented by MCCS, hence only azimuth and elevation are specified.
				type	object
				default	null
				properties
				reference_frame	Co-ordinate system. Must be HORIZON for drift scan.
					type	string
				target_name	Name of target.
					type	string
				az	Pointing azimuth in degrees.
					type	number
				el	Pointing elevation in degrees.
					type	number
				additionalProperties	False
			additionalProperties	False
	additionalProperties	False
csp	CSP configuration specification.
	type	object
	properties
	interface	URI of JSON schema for this command’sJSON payload..
		type	string
	subarray	Subarray elements
		type	object
		default	null
		properties
		subarray_name	Name and scope of current subarray the sub-array.
			type	string
		additionalProperties	False
	common	Common section, containing the parameters and the sections belonging to all CSP subsystems. This section is forwarded to all sub-elements.
		Common configuration schema 2.0
	lowcbf	Correlator and Beamformer specific parameters. This section contains the parameters relevant only for CBF sub-system. This section is forwarded only to CBF subelement.
		default	null
		LOWCBF subarray configurescan 0.1
	pss	Section with parameters to configure the PSS sub-system
		default	null
		PSS configuration 2.0
	pst	Section with parameters to configure the PST sub-system.
		default	null
		LOW PST configure 2.4
	additionalProperties	False
sdp	SDP configuration specification.
	type	object
	properties
	interface	URI of JSON schema for this command’sJSON payload..
		type	string
	scan_type	Scan type string needed on SDP
		type	string
	additionalProperties	False
tmc	TMC configuration specification.
	type	object
	default	null
	properties
	scan_duration	Scan duration in seconds. Value must be >= 0.0
		type	number
	additionalProperties	False
additionalProperties	False

Common configuration schema 2.0

Common section, containing the parameters and the sections belonging to all CSP subsystems. This section is forwarded to all sub-elements.

type	object
properties
config_id	type	string
	default	null
subarray_id	Subarray number
	type	integer
eb_id	Execution block ID to associate scan configs to an observation. This ID is used for associating generated data, especially data products, for a given observation. Multiple scans can be linked to one observation and this ID is used as metadata to associate the data products from all scans of the same observation. This ID does not have to be unique for a scan configuration but should be unique for different observations. For example, all the data and weights files will have an EB_ID header value populated with the value supplied in this field.
	type	string
	pattern	^eb\-[a-z0-9]+\-[0-9]{8}\-[a-z0-9]+$
	default	null
additionalProperties	False

LOWCBF subarray configurescan 0.1

Correlator and Beamformer specific parameters. This section contains the parameters relevant only for CBF sub-system. This section is forwarded only to CBF subelement.

type	object
properties
stations	Subarray Stations and station beam inputdescriptions
	Subarray stations and station beams 0.1
timing_beams	PST beam outputs descriptions
	default	null
	outer 0.1
search_beams	PSS beam outputs descriptions
	type	string
	default	null
visibilities	Visibility output descriptions
	type	object
	default	null
	properties
	fsp	FSPs used for correlation
		type	object
		properties
		function_mode	Firmware name
			type	string
			default	null
		firmware	Firmware name
			type	string
		fsp_ids	List of IDs (integer)
			type	array
			items	type	integer
		additionalProperties	False
	stn_beams	SDP visibility destinations
		type	array
		items	Station beams to correlate 0.1
	additionalProperties	False
zooms	Zoom visibility output descriptions
	type	string
	default	null
additionalProperties	False

Subarray stations and station beams 0.1

Station and station beams parameters

type	object
properties
stns	type	array
	items	type	array
		items	type	integer
stn_beams	type	array
	items	type	object
		properties
		stn_beam_id	station beam id
			type	integer
			default	null
		beam_id	station beam id
			type	integer
		freq_ids	list of station beam frequency ids
			type	array
			items	type	integer
		boresight_dly_poly	URL
			type	string
		additionalProperties	False
additionalProperties	False

outer 0.1

type	object
properties
beams	inner
	type	array
	items	PST beams description 0.1
additionalProperties	False

PST beams description 0.1

type	object
properties
stn_beam_id	Station beam ID for pst beamforming
	type	integer
pst_beam_id	PST beam ID
	type	integer
jones	Jones matrix source URI
	type	string
stn_weights	weights for each station
	type	array
	items	type	number
rfi_enable	Master enable for RFI flagging
	type	array
	default	null
	items	type	boolean
rfi_static_chans	Freqency IDs to be always flagged
	type	array
	default	null
	items	type	integer
rfi_dynamic_chans	Frequency IDs to be dynamically flagged
	type	array
	default	null
	items	type	integer
rfi_weighted	Parameter for dynamic flagging
	type	number
	default	null
firmware	Firmware name
	type	string
	default	null
offset_dly_poly	Delay polynomial source URI
	type	string
additionalProperties	False

Station beams to correlate 0.1

type	object
properties
stn_beam_id	Station Beam ID
	type	integer
integration_ms	milliseconds integration
	type	integer
additionalProperties	False

PSS configuration 2.0

type	object
properties
dummy_param	type	string
	default	null
additionalProperties	False

LOW PST configure 2.4

Main configuration for the Low CSP Pulsar timing sub-system

type	object
properties
beams	List of PST Beams IDs to configure
	type	array
	items	Parameters to configure the PST sub-system
		type	object
		properties
		beam_id	Configuration for a PST beam ID
			type	integer
		scan	Parameters to configure the scan
			PST scan configuration 2.4
		beam	Parameter to configure the beam
			default	null
			PST beam configuration 2.4
		additionalProperties	False
additionalProperties	False

PST scan configuration 2.4

Pulsar Timing specific scan configuration parameters.

type	object
properties
activation_time	Date and time when to start the PST reconfiguration. Units: UTC timestamp Keyword: ACTIVATION_TIME
	type	string
timing_beam_id	Identifier assigned by LMC/TM used to identify the beam configuraiton. PST selects which PST server to use for this scan and timing beam, and provides a mapping from the timing beam identifier by the TM to PST capability id. Keyword: BEAM
	type	string
	default	null
bits_per_sample	The number of bits per complex-values time sample in the CBF output data. Valid values are 16, 24, or 32. Keyword: NBIT
	type	integer
num_of_polarizations	The number of polarizations in the CBF output data. Valid values are 1 or 2. Keyword: NPOL
	type	integer
udp_nsamp	The number of time samples for each single polarization and the a single frequency in each UDP packet sent by CBF. Note: this must be an integer multiple of WT_NSMAP Range: 4 (Low), 32 (Mid) Keyword: UDP_NSAMP
	type	integer
wt_nsamp	The number of time samples described by as single relative weight. There is a unique relative weight for each frequency channel, and each relative weight describes both polarizations. Range: 4 (Low), 32 (Mid) Keyword: WT_NSAMP
	type	integer
udp_nchan	The number of contiguous frequency channels in each UDP packet sent by CBF. Range: 24 (Low), 185 (Mid) Keyword: UDP_NCHAN
	type	integer
num_frequency_channels	The total number of frequency channels into which the total critical bandwidth has been divided. This must be an integer multiple of udp_nchan Range: 1 to 82944 Keyword: OBSNCHAN
	type	integer
centre_frequency	Centre frequency of to the total (critical) bandwidth spanned by the frequency channels. Units: Hz Range: 50e6 to 12800e6 Keyword: OBSFREQ
	type	number
total_bandwidth	Total (critical) bandwidth spanned by the channels of the observation. Low: 0.00361 to 300 MHz Mid: 0.053.76 to 2500 MHz Units: Hz Range: 3610 to 2.5e9 Keyword: OBSBW
	type	number
observation_mode	The observation mode used for the scan. The value VOLTAGE_RECORDER is added for AA0.5, while the other values will be needed for in the future for data processing. Keyword: OBSMODE
	allOf	type	string
		enum	PULSAR_TIMING, DYNAMIC_SPECTRUM, FLOW_THROUGH, VOLTAGE_RECORDER
observer_id	The observer in charge of the observations. Keyword: OBSERVER
	type	string
project_id	The project that the observations are for. Keyword: PROJID
	type	string
pointing_id	The ID for the sub-array pointing. Keyword: PNT_ID
	type	string
source	The name of the source. Keyword: SRC_NAME
	type	string
itrf	The International Terrestrial Reference Frame (ITRF) coordinates of the telescope delay centre. Units: metres Keyword: ITRF
	type	array
	items	type	number
receiver_id	The receiver name or ID (instrument). Keyword: FRONTEND
	type	string
feed_polarization	The native polarization of feed. Range: LIN or CIRC Keyword: FD_POLN
	allOf	type	string
		enum	LIN, CIRC
feed_handedness	Code for sense of feed. For value of +1 for XYZ forming RH set with Z in the direction of propagation. Looking up into the feed of a prime-focus receiver or at the sky). For FD_HAND = +1, the rotation from A (or X) to B (or Y) is counter clockwise or in the direction of increasing Feed Angle (FA) or Position Angle (PA). For circular feeds, FD_HAND = +1 for IEEE LCP on the A (or X) probe. Range: -1 or +1 Keyword: FD_HAND
	allOf	type	integer
		enum	-1, 1
feed_angle	Feed angle of the E-vector for an equal in-phase response from the A(X) and B(Y) probes, measured in the direction of increasing feed angle or position angle (clockwise when looking down on a prime focuse receiver). Units: degrees Range: -180 to 180. Keyword: FD_SANG
	type	number
feed_tracking_mode	The tracking mode for the feed: FA - constant feed angle and that the feed stays fixed with respect to the telescope’s reference frame. CPA - the feed rotates to maintain a constant phase angle (i.e. it tracks the variation of the parallactic angle.). When the cordinate mode is GALATIC, PA is with respect to Galactic north and similarly for coordinate mode ECLIPTIC then PA is with respect to ecliptic north. SPA - the feed angle is held fixed at an angle such that the requested PA is obtained at the mid-point of the observation. TPA - is only relevant for scan observations - the feed is rotated to maintain a constant angle with respect to the scan direction. Range: FA, CPA, SPA, or TPA Keyword: FD_MODE
	allOf	type	string
		enum	FA, CPA, SPA, TPA
feed_position_angle	The requested angle of feed reference. For feed_mode = ‘FA’ this is respect to the telescope’s reference frame (feed_angle = 0), and for feed_mode = ‘CPA’ this is with respect to the celestial north (parallic angle = 0) or with respect to the Galactic north for coordinate_mode = ‘GALACTIC’. Range: -180 to +180. Keyword: FA_REQ
	type	number
oversampling_ratio	The oversampling ratio expressed as a fraction as an array of int, with the first value the numerator and the second is the denominator. (e.g. 8/7 is assigned as [8,7]). Range: 8/7 or 4/3 Keyword: OVERSAMP
	type	array
	items	type	integer
coordinates	The tied-array beam’s tracking co-ordinates. As of version 2.2 of the schema this only handles equitorial tracking which means uses RA/Dec J2000.0 coords but PST may support different tracking modes and coordinates the future.
	PST RA_Dec coordinates 2.4
max_scan_length	The maximum length of the observation. Units: seconds Range: 30 - 43200 Keyword: SCANLEN_MAX
	type	number
subint_duration	The length of each output sub-integration. Units: seconds Range: 1 - 60 Keyword: OUTSUBINT
	type	number
receptors	An array of receptor IDs for the receptors included in the sub-array. Keyword: ANTENNA
	type	array
	items	type	string
receptor_weights	Weight for each receptor. Range: 0 - 1.0 Keyword: ANT_WEIGHTS
	type	array
	items	type	number
num_rfi_frequency_masks	The number of frequency ranges to be masked. Range: 0 - 1024 Keyword: NMASK
	type	integer
	default	0
rfi_frequency_masks	A two-dimensional array of length of num_frequency_mask of known RFI frequency ranges to excise from the data. The array contains mask pairs of [f_min, f_max] pairs for known frequency ranges containing RFI not excised by the CBF. The overall dimension of this array is num_frequency_mask x 2. Units: Hz Keyword: FREQ_MASK
	type	array
	default	null
	items	type	array
		items	type	number
destination_address	The destination address for the PST output data. Includes IPv4 Address, port number.
	type	array
	default	null
	items	anyOf	type	string
			type	integer
test_vector_id	Identifier for a test vectore that will be present in the tied-array beam data stream beam CBF and PST. Keyword: TEST_VECTOR
	type	string
	default	null
pt	Pulsar Timing specific parameters for the ‘PULSAR_TIMING’ mode configuration.
	default	null
	PST ‘PULSAR_TIMING’ mode configuration 2.4
ds	Pulsar Timing specific parameters for the ‘DYNAMIC_SPECTRUM’ mode configuration.
	default	null
	PST ‘DYNAMIC_SPECTRUM’ mode configuration 2.4
ft	Pulsar Timing specific parameters for the ‘FLOW_THROUGH’ mode configuration.
	default	null
	PST ‘FLOW_THROUGH’ mode configuration 2.4
num_channelization_stages	The number of stages used to channelize the data: e.g. * for Low, there are 2 stages: 1 in LFAA and 1 in CBF * for Mid, there are 2 stages: 1 in FSP and 1 in PST BF. Keyword: NSTAGE
	type	integer
channelization_stages	List of configuration for each channelization stage.
	type	array
	items	Pulsar Timing specific parameters for channelization stage configuration.
		PST channelization stage configuration 2.4
additionalProperties	False

PST RA_Dec coordinates 2.4

Pulsar Timing specific parameters for RA/Dec tracking coordinates.

type	object
properties
equinox	The coordinate epoch. This can be in Julian date or Modified Julian Date. Units: years Range: >= 2000 Keyword: EQUINOX
	type	number
	default	2000.0
ra	The Right Accession (RA) of the coordinates used for tracking. Valid formats is ‘hh:mm:ss.sss’ or ‘ddd.ddd’ Keyword: STT_CTD1
	type	string
dec	The declination (Dec) of the coordinates used for tracking. Valid formats is ‘hh:mm:ss.sss’ or ‘ddd.ddd’ Keyword: STT_CTD2
	type	string
additionalProperties	False

PST ‘PULSAR_TIMING’ mode configuration 2.4

Pulsar Timing specific parameters for the ‘PULSAR_TIMING’ mode configuration.

type	object
properties
dispersion_measure	The dispersion measure for coherent/inchoerent de-dispersion. Units: pccm^-3 Range: 0 - 100000 Keyword: DM
	type	number
rotation_measure	The rotation measure for phase-coherent Faraday rotation correction. Units: radians per metre squared Keyword: RM
	type	number
	default	null
ephemeris	The ephemeris of the pulsar being observed. Units: PSRCAT compatible ASCII string Keyword: EPHEMERIS
	type	string
pulsar_phase_predictor	Pulsar phase predictor generated from ephemeris. Units: TEMPO2 compatible ASCII string Keyword: PREDICTOR
	type	string
output_frequency_channels	The number of output frequency channels. This must be between 1 and the number of observation channels. Keyword: OUTNCHAN
	type	integer
output_phase_bins	The number of output phase bins. Range: 64 - 2048 Keyword: OUTNBIN
	type	integer
num_sk_config	The number of spectral kurtosis (SK) configurations to apply. Keyword: N_SK
	type	integer
sk_config	List of spectral kurtosis configurations.
	type	array
	items	Pulsar Timing specific parameters for the spectral kurtosis (SK) for the ‘PULSAR_TIMING’ mode.
		PST spectral kurtosis configuration 2.4
target_snr	The signal-to-noise ratio (SNR) of the on-pulse flux for the scan. May be used to prematurely end a scan when the integrated SNR reaches the target. A value of 0 indicates there is no limit. Keyword: TARGET_SNR
	type	number
additionalProperties	False

PST spectral kurtosis configuration 2.4

Pulsar Timing specific parameters for the spectral kurtosis (SK) for the ‘PULSAR_TIMING’ mode.

type	object
properties
sk_range	Frequency ranges for each spectral kurtosis (SK) configuration. Units: Hz Keyword: SK_RNG
	type	array
	items	type	number
sk_integration_limit	The number of input time samples integrated into each spectral kurtosis (SK) statistic. Range: 64 - 1024 Keyword: SK_INTS
	type	integer
sk_excision_limit	Spectral kurtosis excision limits (RFI threshold) in units of standard deviations. Range: 1 - 100 Keyword: SK_EXIS
	type	number
additionalProperties	False

PST ‘DYNAMIC_SPECTRUM’ mode configuration 2.4

Pulsar Timing specific parameters for the ‘DYNAMIC_SPECTRUM’ mode configuration.

type	object
properties
dispersion_measure	The dispersion measture for coherent/inchoerent de-dispersion. This is only required for pulsar timing and dynamic spectrum modes. Range: [0, 100000] Keyword: DM
	type	number
rotation_measure	The rotation measure for phase-coherent Faraday rotation correction. Units: radians per metre squared Keyword: RM
	type	number
	default	null
output_frequency_channels	The number of output frequency channels. This must be between 1 and the number of observation channels. Keyword: OUTNCHAN
	type	integer
stokes_parameters	The Stokes parameters to output when in Dynamic spectrum mode. Range: string with a combination of I, Q, U, and V. Keyword: STOKES_FB
	type	string
num_bits_out	The number of bits per output sample. Range: 1, 2, 4, 8, 16 or 32 Keyword: NBIT_OUT
	allOf	type	integer
		enum	1, 2, 4, 8, 16, 32
time_decimation_factor	The number of input samples per output time sample when in Dynamic Spectrum mode. Keyword: TDEC_FB
	type	integer
frequency_decimation_factor	The number of input frequency channels incoherently added to each output frequency channel in Dynamic Spectrum. This is required in addition to output_frequency_channels because some frequency channels may be merged coherently to increase temporal resolution. Keyword: FDEC_FB
	type	integer
num_sk_config	The number of spectral kurtosis (SK) configurations to apply. Keyword: N_SK
	type	integer
	default	null
sk_config	List of spectral kurtosis configurations.
	type	array
	default	null
	items	Pulsar Timing specific parameters for the spectral kurtosis (SK) for the ‘PULSAR_TIMING’ mode.
		PST spectral kurtosis configuration 2.4
requantisation_scale	Scale factor to govern the dynamic range for fixed precision output to be applied during re-quantisation. Keyword: DIGITIZER_SCALE
	type	number
requantisation_length	Length of data to be used when determining the scaling factors used for fixed precision output during re-quantisation. Units: seconds Keyword: DIGITIZER_LENGTH
	type	number
additionalProperties	False

PST ‘FLOW_THROUGH’ mode configuration 2.4

Pulsar Timing specific parameters for the ‘FLOW_THROUGH’ mode configuration.

type	object
properties
num_bits_out	The number of bits per output sample. Range: 1, 2, 4, 8, 16 or 32 Keyword: NBIT_OUT
	allOf	type	integer
		enum	1, 2, 4, 8, 16, 32
channels	The indices of the first and last (inclusive) frequency channels that define the single contiguous range of frequency channels to be recorded. Keyword: CHAN_FT
	type	array
	items	type	integer
requantisation_scale	Scale factor applied during re-quantisation that modifies the dynamic range of the fixed precision output. By default, for 2, 4, and 8 bits per sample, data will be scaled to minimize scattered power by adopting the Optimum Input Threshold Spacing for a Uniform Digitizer defined in Table 3 of Jenet & Anderson (1998; PASP 110:1467). For 16 and 32 bits per sample, by default the data will be scaled such that the maximum fixed precision output value (2^{num_bits_out-1}) corresponds to 6 times the standard deviation. For all num_bits_out, the standard deviation is that of either the real or imaginary part of each complex-valued sample. The default scale factor is computed such that, after multiplication by this scale factor, the data would satisfy the conditions described above. This default scale factor is multiplied by requantisation_scale. Therefore, a requantisation_scale value greater than 1 increases the value of the floating point data before it is cast to a fixed precision value, thereby reducing the overhead available to represent RFI and increasing the probability of clipping. Keyword: DIGITIZER_SCALE
	type	number
num_channels	The number of input channels to be recorded. This value must be less than or equal to the output_frequency_channels. Keyword: NCHAN_FT
	type	integer
requantisation_length	Length of data to be used when determining the scaling factors used for fixed precision output during re-quantisation. Units: seconds Keyword: DIGITIZER_LENGTH
	type	number
additionalProperties	False

PST channelization stage configuration 2.4

Pulsar Timing specific parameters for channelization stage configuration.

type	object
properties
num_filter_taps	Total number of taps in the prototype filter (i.e. over all arms) used in the stage. Keyword: NSTAP_k
	type	integer
filter_coefficients	An array of filter coefficients that define the (time domain) response function of the prototype filter used in the stage. Length of this is num_filter_taps. Keyword: COEFF_k
	type	array
	items	type	number
num_frequency_channels	The number of frequency channels output by each polyphase filter bank (PFB) for this stage. Keyword: NCHAN_PFB_k
	type	integer
oversampling_ratio	The oversampling ratio expressed as a fraction as an array of int, with the first value the numerator and the second is the denominator. (e.g. 8/7 is assigned as [8,7]). Keyword: OVERSAMP_k
	type	array
	items	type	integer
additionalProperties	False

PST beam configuration 2.4

Pulsar Timing specific beam configuration parameters.

As of version 2.3 this schema has no elements and is deprecated

type	object
properties
additionalProperties	False