Mid TMC configure 2.2

Example JSON.

{
    "interface": "https://schema.skao.int/ska-tmc-configure/2.2",
    "transaction_id": "txn-....-00001",
    "pointing": {
        "target": {
            "reference_frame": "ICRS",
            "target_name": "Polaris Australis",
            "ra": "21:08:47.92",
            "dec": "-88:57:22.9",
            "ca_offset_arcsec": 0.0,
            "ie_offset_arcsec": 0.0
        }
    },
    "dish": {
        "receiver_band": "1"
    },
    "csp": {
        "interface": "https://schema.skao.int/ska-csp-configure/2.0",
        "subarray": {
            "subarray_name": "science period 23"
        },
        "common": {
            "config_id": "sbi-mvp01-20200325-00001-science_A",
            "frequency_band": "1",
            "subarray_id": 1
        },
        "cbf": {
            "fsp": [{
                "fsp_id": 1,
                "function_mode": "CORR",
                "frequency_slice_id": 1,
                "integration_factor": 1,
                "zoom_factor": 0,
                "channel_averaging_map": [
                    [0, 2],
                    [744, 0]
                ],
                "channel_offset": 0,
                "output_link_map": [
                    [0, 0],
                    [200, 1]
                ]
            }, {
                "fsp_id": 2,
                "function_mode": "CORR",
                "frequency_slice_id": 2,
                "integration_factor": 1,
                "zoom_factor": 1,
                "zoom_window_tuning": 650000,
                "channel_averaging_map": [
                    [0, 2],
                    [744, 0]
                ],
                "channel_offset": 744,
                "output_link_map": [
                    [0, 4],
                    [200, 5]
                ]
            }],
            "vlbi": {}
        },
        "pss": {},
        "pst": {}
    },
    "sdp": {
        "interface": "https://schema.skao.int/ska-sdp-configure/0.4",
        "scan_type": "science_A"
    },
    "tmc": {
        "scan_duration": 10.0,
        "partial_configuration": false
    }
}

https://schema.skao.int/ska-tmc-configure/2.2

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

  • pointing

Pointing Mid TMC configure 2.2

Pointing configuration specification.

type

object

properties

  • target

Target TMC configure 2.2

DEPRECATED

Target coordinates

This field has been superseded by pointing.groups and is deprecated from schema version 4.1.

If pointing.groups is present, any value provided in pointing.target will be ignored.

type

object

properties

  • reference_frame

standard celestial reference system such as ICRS

type

string

  • target_name

celestial source

type

string

  • ra

Pointing Right Ascension coordinates.

type

string

  • dec

Pointing Declination coordinates.

type

string

  • ca_offset_arcsec

Cross-elevation offset in arcseconds from the central pointing pointing defined by target’s ra+dec.

This is an optional field; if omitted, an offset of 0 arcseconds can be assumed.

type

number

  • ie_offset_arcsec

Elevation offset in arcseconds from the central pointing position defined by the ra+dec pair.

This is an optional field; if omitted, an offset of 0 arcseconds can be assumed.

type

number

additionalProperties

True

additionalProperties

True

  • csp

CSP config 2.0

CSP configuration specification.

type

object

properties

  • interface

type

string

  • subarray

subarray 2.0

subarray section, containing the parameters relevant only for the current sub-array device. This section is not forwarded to any subelement.

type

object

properties

  • subarray_name

Name and scope of current subarray the sub-array.

type

string

additionalProperties

False

  • pss

PSS configuration schema 0.0

type

object

properties

  • dummy_param

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

  • cbf

Correlator and Beamformer specific parameters. This section contains the parameters relevant only for CBF sub-element. This section is forwarded only to CBF subelement. Most of it to be borrowed from IICD

CBF_config_2.0

  • pst

PST configuration 2.0

PST specific parameters. To be borrowed from IICD

type

object

properties

  • dummy_param

type

string

additionalProperties

False

additionalProperties

False

  • sdp

SDP configure 1.0

SDP configuration specification.

type

object

properties

  • interface

type

string

  • transaction_id

type

string

  • scan_type

type

string

  • new_scan_types

type

array

items

A scan configuration for SDP. Once AssignResources has been performed successfully, subsequent Configure commands can select from these scan types in order to coordinate SDP with other sub-systems participating in the observation - for instance to switch between targets, or perform special calibration scans.

Scan_type_1.0

additionalProperties

True

  • tmc

TMC configure 2.2

TMC Mid TMC configuration specification.

type

object

properties

  • scan_duration

Scan duration in seconds.

Value must be >= 0.0

allOf

type

number

  • partial_configuration

Partial Configuration Flag.

Partial configurations assume that previously set state is maintained, and undergo less strict JSON validation.

type

boolean

additionalProperties

True

  • dish

Dish band configuration

type

object

properties

  • receiver_band

Dish Receiver band configuration

type

string

additionalProperties

True

additionalProperties

True

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

  • 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]+$

  • band_5_tuning

Center frequency for the Band-of-Interest. Required if Band is 5a or 5b; not specified for other Bands (not configurable for Band 1 and 2).

Input for Band 5a and 5b consists of two 2.5 GHz streams; the center frequency can be independently tuned for each stream.

The following nomenclature is used to refer to Band 5a and 5b streams: 5a1, 5a2, 5b1, 5b2.

type

array

items

type

number

  • frequency_band

Frequency band applies for all the receptors (VCCs) that belong to the sub-array.

type

string

pattern

^(1|2|3|4|5(a|b))$

additionalProperties

False

CBF_config_2.0

Correlator and Beamformer specific parameters. This section contains the parameters relevant only for CBF sub-element. This section is forwarded only to CBF subelement. Most of it to be borrowed from IICD

type

object

properties

  • frequency_band_offset_stream1

Optionally, an offset can be specified so that the entire observed band is shifted (to accommodate a Zoom Window that crosses a ‘natural’ Frequency Slice boundary). If specified, applies for all the receptors in the sub-array.

Bands 1 and 2: input from the receptor consists of a single data stream; the Frequency Band Offset (FBO) should be specified for Stream 1 only.

Bands 5a and 5b: input from the receptor consists of two data streams; the FBO can be specified for each stream independently. Note: For Band 5a and 5b the frequency shift is performed by the receptor (DISH).

Note: This is optional and does not need to be implemented in PI3, but would be great for demo; if Team Buttons is looking for opportunities to showcase interesting GUIs, Zoom Windows are perfect opportunity (would require TMC and CSP to support these two parameters, corrBandwidth values > 0 and zoom window tuning.)

type

integer

  • frequency_band_offset_stream2

See frequencyBandOffsetStream1

type

integer

  • delay_model_subscription_point

FQDN of TMC.DelayModel TANGO attribute which exposes delay values for all the dishes assigned to a Subarray in JSON format. Delay values are updated every 10 seconds.

type

string

  • doppler_phase_corr_subscription_point

The same model applies for all receptors that belong to the subarray. Delivered by TMC using publish-subscribe mechanism (see ICD Section 3.8.8.5.3). The Doppler phase correction, by default, applies only to the CSP_Mid Processing Mode Correlation; optionally may apply to other Processing Modes as well.

type

string

  • rfi_flagging_mask

Specified as needed in advance of the scan start and/or during the scan. Delivered using publish-subscribe mechanism (see ICD Section 3.8.8.5.7).

type

object

properties

additionalProperties

False

  • fsp

type

array

items

FSP_config_2.0

  • vlbi

Very Long Baseline Interferometry specific parameters. To be borrowed from IICD This section contains the parameters relevant only for VLBI. This section is forwarded only to CSP subelement.

VLBI_config_2.0

  • search_window

type

array

items

Up to two 300 MHz Search Windows can be optionally configured and used as input for Transient Data Capture and/or Pulsar Search beam-forming.

Search_window_config_2.0

additionalProperties

False

FSP_config_2.0

type

object

properties

  • fsp_id

type

integer

  • function_mode

allOf

type

string

enum

CORR, PSS-BF, PST-BF, VLBI

  • receptors

Optionally a subset of receptors to be correlated can be specified. If not specified, all receptors that belong to the subarray are cross-correlated (i.e. visibilities for all the baselines in the subarray are generated and transmitted to SDP).

Valid receptor IDs include: SKA dishes: “SKAnnn”, where nnn is a zero padded integer in the range of 001 to 133. MeerKAT dishes: “MKTnnn”, where nnn is a zero padded integer in the range of 000 to 063.

type

array

items

type

string

pattern

^(SKA(00[1-9]|0[1-9][0-9]|1[0-2][0-9]|13[0-3]))|

(MKT(0[0-5][0-9]|06[0-3]))$

  • frequency_slice_id

Frequency Slice to be processed on this FSP (valid range depends on the Frequency Band).

type

integer

  • zoom_factor

Bandwidth to be correlated calculated as FSBW/2n, where n is in range [0..6].

When n=0 the full Frequency Slice bandwidth is correlated.

BW > 0 implies ‘Zoom Window’ configuration; the spectral Zoom Window tuning must be specified.

type

integer

  • zoom_window_tuning

The Zoom Window tuning provided in absolute terms as RF center frequency. Based on that, CSP_Mid calculates tuning within the data stream received from the receptor. Must be selected so that the entire Zoom Window is within the Frequency Slice. If partially out of the FS a warning is generated. If completely outside of the FS an exception is generated.

Step size <= 0.01MHz. The Frequency Band Offset can be used to shift the entire observed band in order to accommodate a Zoom Window that spans across a Frequency Slice boundary.

type

integer

  • integration_factor

Integration time for the correlation products, defines multiple of 140 milliseconds.

type

integer

  • output_mac

Output MAC address to send visibilities to for every channel, given as a list of start channel ID to IEEE 802 MAC addresses. Where no value is given for a concrete channel, the previous value should be used.

type

array

items

type

array

items

anyOf

type

integer

type

string

  • channel_averaging_map

Table of up to 20 x 2 integers. Each of entries contains:

  • Start channel ID, and

  • averaging factor.

Explanation: Each FSP produces 14880 (TBC) fine channels across the correlated bandwidth (Frequency Slice or Zoom Window). Channels are evenly spaced in frequency.

TM shall provide the table that for each FSP and each group of 744 channels (there are 20 groups per FSP) indicates the channel averaging factor. More precisely, for each group the TMC provided table specifies:

  • the channel ID (integer) of the first channel, and

  • the averaging factor, as follows:

  • 0 means do not send channels to SDP,

  • 1 means no averaging,

  • 2 means average two adjacent channels,

  • 3 means average three adjacent channels,

and so on.

If no entry is present for an FSP, the averaging settings of the previous FSP are still applicable.

type

array

items

type

array

items

type

integer

  • channel_offset

Channel ID to use for visibilities of the first channel produced by this FSP. For example, if the channel offset is 5000 the first channel group would span IDs 5000-5743.

Note that this offset does not apply to channel maps in this structure (such as channelAveragingMap or outputHost).

type

integer

  • output_link_map

Output links to emit visibilities on for every channel, given as a list of start channel ID to link ID. Where no value is given for concrete channel, the previous value should be used.

type

array

items

type

array

items

anyOf

type

integer

type

string

  • output_host

Output host to send visibilities to for every channel, given as a list of start channel ID to host IP addresses in dot-decimal notation. Where no value is given for a concrete channel, the previous value should be used.

type

array

items

type

array

items

anyOf

type

integer

type

string

  • output_port

Output port to send visibilities to for every channel, given as a list of start channel ID to port number. Where no value is given for a concrete channel, the previous value should be used.

type

array

items

type

array

items

type

integer

additionalProperties

False

VLBI_config_2.0

Very Long Baseline Interferometry specific parameters. To be borrowed from IICD This section contains the parameters relevant only for VLBI. This section is forwarded only to CSP subelement.

type

object

properties

  • dummy_param

type

string

additionalProperties

False

Search_window_config_2.0

Up to two 300 MHz Search Windows can be optionally configured and used as input for Transient Data Capture and/or Pulsar Search beam-forming.

type

object

properties

  • search_window_id

Identifier of the 300MHz Search Window. Unique within a sub-array.

type

integer

  • search_window_tuning

The Search Window tuning is provided in absolute terms as RF center frequency. The Search Window must be placed within the observed band. If partially out of the observed Band a warning is generated. If completely outside of the observed Band an exception is generated.

type

integer

  • tdc_enable

Enable / disable Transient Data Capturefor the Search Window.

type

boolean

  • tdc_num_bits

Number of bits per sample (for the Transient Data Capture). Required if TDC is enabled, otherwise not specified.

type

integer

  • tdc_period_before_epoch

Users can trade the period of time for which data are saved and transmitted for the sample bit-width and/or the number of Search Windows. The exact information regarding the memory capacity per receptor and supported range will be provided in construction.

The epoch is specified in the command that triggers TDC off-loading (transmission of data).

type

integer

  • tdc_period_after_epoch

see tdcPeriodBeforeEpoch

type

integer

  • tdc_destination_address

Destination addresses (MAC, IP, port) for off-loading of the content of the Transient Data Capture Buffer, specified per receptor. The destination addresses for the content of the Transient Data Capture can be provided either as a part of the scan configuration or by the command that triggers transmission of the captured data. The latter, if provided, overrides previously set addresses.

Required if TDC is enabled, otherwise not specified.

type

array

items

anyOf

type

integer

type

string

additionalProperties

False

Scan_type_1.0

A scan configuration for SDP. Once AssignResources has been performed successfully, subsequent Configure commands can select from these scan types in order to coordinate SDP with other sub-systems participating in the observation - for instance to switch between targets, or perform special calibration scans.

type

object

properties

  • scan_type_id

type

string

  • reference_frame

Specification of the reference frame or system for a set of pointing coordinates (see ADR-49)

type

string

  • ra

Right Ascension in degrees (see ADR-49)

type

string

  • dec

Declination in degrees (see ADR-49)

type

string

  • channels

type

array

items

Informs SDP ingest about the expected channel configuration, especially which frequencies are expected to be mapped to which channel ID. Note that channel IDs are not guaranteed to be continuous, so this might involve gaps and/or strides.

Scan_channels_1.0

additionalProperties

True

Scan_channels_1.0

Informs SDP ingest about the expected channel configuration, especially which frequencies are expected to be mapped to which channel ID. Note that channel IDs are not guaranteed to be continuous, so this might involve gaps and/or strides.

type

object

properties

  • count

Number of channels

type

integer

  • start

First channel ID

type

integer

  • stride

Distance between subsequent channel IDs

type

integer

  • freq_min

Lower bound of first channel

type

number

  • freq_max

Upper bound of last channel

type

number

  • link_map

Channel map that specifies which network link is going to get used to send channels to SDP. Intended to allow SDP to optimise network and receive node configuration.

type

array

items

additionalProperties

True