CSP configurescan 0.1
JSON schema and example for CSP Mid configure
CSP config 0.1
Example JSON (TMC input)
{
"id": "sbi-mvp01-20200325-00001-science_A",
"frequencyBand": "1",
"fsp": [{
"fspID": 1,
"functionMode": "CORR",
"frequencySliceID": 1,
"integrationTime": 1400,
"corrBandwidth": 0,
"channelAveragingMap": [
[0, 2],
[744, 0]
],
"fspChannelOffset": 0,
"outputLinkMap": [
[0, 0],
[200, 1]
]
}, {
"fspID": 2,
"functionMode": "CORR",
"frequencySliceID": 2,
"integrationTime": 1400,
"corrBandwidth": 0,
"channelAveragingMap": [
[0, 2],
[744, 0]
],
"fspChannelOffset": 744,
"outputLinkMap": [
[0, 4],
[200, 5]
]
}]
}
Example JSON (CSP configuration for science_a scan)
{
"id": "sbi-mvp01-20200325-00001-science_A",
"frequencyBand": "1",
"fsp": [{
"fspID": 1,
"functionMode": "CORR",
"frequencySliceID": 1,
"integrationTime": 1400,
"corrBandwidth": 0,
"channelAveragingMap": [
[0, 2],
[744, 0]
],
"fspChannelOffset": 0,
"outputLinkMap": [
[0, 0],
[200, 1]
],
"outputHost": [
[0, "192.168.0.1"],
[400, "192.168.0.2"]
],
"outputMac": [
[0, "06-00-00-00-00-00"]
],
"outputPort": [
[0, 9000, 1],
[400, 9000, 1]
]
}, {
"fspID": 2,
"functionMode": "CORR",
"frequencySliceID": 2,
"integrationTime": 1400,
"corrBandwidth": 0,
"channelAveragingMap": [
[0, 2],
[744, 0]
],
"fspChannelOffset": 744,
"outputLinkMap": [
[0, 4],
[200, 5]
],
"outputHost": [
[0, "192.168.0.3"],
[400, "192.168.0.4"]
],
"outputMac": [
[0, "06-00-00-00-00-01"]
],
"outputPort": [
[0, 9000, 1],
[400, 9000, 1]
]
}]
}
Example JSON (CSP configuration for cal_a scan)
{
"id": "sbi-mvp01-20200325-00001-science_A",
"frequencyBand": "1",
"fsp": [{
"fspID": 1,
"functionMode": "CORR",
"frequencySliceID": 1,
"integrationTime": 1400,
"corrBandwidth": 0,
"channelAveragingMap": [
[0, 2],
[744, 0]
],
"fspChannelOffset": 0,
"outputLinkMap": [
[0, 0],
[200, 1]
],
"outputHost": [
[0, "192.168.1.1"]
],
"outputPort": [
[0, 9000, 1]
]
}, {
"fspID": 2,
"functionMode": "CORR",
"frequencySliceID": 2,
"integrationTime": 1400,
"corrBandwidth": 0,
"channelAveragingMap": [
[0, 2],
[744, 0]
],
"fspChannelOffset": 744,
"outputLinkMap": [
[0, 4],
[200, 5]
],
"outputHost": [
[0, "192.168.1.1"]
],
"outputPort": [
[0, 9744, 1]
]
}]
}
type |
object |
||
properties |
|||
|
type |
string |
|
|
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 |
||
|
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 applies for all the receptors (VCCs) that belong to the sub-array. |
||
type |
string |
||
|
type |
array |
|
items |
|||
additionalProperties |
True |
||
FSP_config_0.1
type |
object |
|||||
properties |
||||||
|
type |
integer |
||||
|
type |
string |
||||
|
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 |
||||
|
Frequency Slice to be processed on this FSP (valid range depends on the Frequency Band). |
|||||
type |
integer |
|||||
|
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 |
|||||
|
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 time for the correlation products, defines multiple of 140 milliseconds. |
|||||
const |
1400 |
|||||
|
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 |
allOf |
type |
array |
|||
items |
anyOf |
type |
integer |
|||
type |
string |
|||||
|
Table of up to 20 x 2 integers. Each of entries contains:
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:
and so on. If no entry is present for an FSP, the averaging settings of the previous FSP are still applicable. |
|||||
type |
array |
|||||
items |
allOf |
type |
array |
|||
items |
type |
integer |
||||
|
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 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 |
allOf |
type |
array |
|||
items |
anyOf |
type |
integer |
|||
type |
string |
|||||
|
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 |
allOf |
type |
array |
|||
items |
anyOf |
type |
integer |
|||
type |
string |
|||||
|
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 |
allOf |
type |
array |
|||
items |
type |
integer |
||||
additionalProperties |
True |
|||||