TMC Mid Deployment

TMC Mid deployment comes with following components:

1. Central Node

2. Subarray Node

3. Csp Master Leaf Node

4. Csp Subarray Leaf Node

5. Sdp Master Leaf Node

6. Sdp Subarray Leaf Node

7. Dish Leaf Node

Configurable options

• 1. instances : User can provide the array of device server deployment instances required for node.

  Default for nodes are:

  1. Central Node : [“01”]

  2. Csp Master Leaf Node : [“01”]

  3. Sdp Master Leaf Node : [“01”]

• 2. subarray_count : User can set this subarray count according to number of device server deployment instances required for node.

  Default value for nodes is 2.

  1. Subarray Node

  2. Csp Subarray Leaf Node

  3. Sdp Subarray Leaf Node

• 3. dish_name : User can set this by providing the list of TRLS using global.namespace_dish.dish_names

  Default Value for dish leaf node is

  1. Dish Leaf Node : [“001”, “036”, “063”, “100”]

• 4. file : User can provide custom device server configuration file to nodes.Default is configuration files

• 5. enabled : User can opt to disable any node by setting this value to False.Default is True for all nodes.

• 6. Variables under global section

  1. tmc_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of SubarrayNode.

  2. csp_subarray_ln_prefix : This value is present under global, User can use this to change the FQDN prefix of CspSubarrayLeafNode.

  3. sdp_subarray_ln_prefix : This value is present under global, User can use this to change the FQDN prefix of SdpSubarrayLeafNode.

  4. csp_master_ln : This value is present under global, User can use this to change the FQDN of CspMasterLeafNode.

  5. sdp_master_ln : This value is present under global, User can use this to change the FQDN of SdpMasterLeafNode.

  6. csp_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of CSP Subarray.

  7. sdp_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of SDP Subarray.

  8. csp_master : This value is present under global, User can use this to change the FQDN of CSP Master.

  9. sdp_master : This value is present under global, User can use this to change the FQDN of SDP Master.

  10. dish_suffix : This value is present under global, User can use this to change the FQDN suffix of Dish Master.

  11. dish_ln_prefix : This value is present under global, User can use this to change the FQDN prefix of DishLeafNode.

• 7. Variables under deviceServers.centralnode section

  1. DishIDs : User can set this value to provide the ID’s of dishes present in the deployment. Default is [“SKA001”, “SKA036”, “SKA063”, “SKA100”]

  2. Variables under DishVccConfig section

     1. DishVccUri : This refers to the URI for Dish VCC Configuration. Currently defaults to “car://gitlab.com/ska-telescope/ska-telmodel-data?ska-sdp-tmlite-repository-1.0.0#tmdata”.

     2. DishVccFilePath : This refers to the file path for Dish VCC Configuration. Currently defaults to “instrument/ska1_mid_psi/ska-mid-cbf-system-parameters.json”.

     3. DishKvalueAggregationAllowedPercent : This refers to the percentage of the dishes to be considered for DishKValue aggregation. Currently all the dishes are considered therefore defaults to “100.0”.

  3. Variables under KValueValidRange section

     1. min : This refers to the lower limit of the valid k-value range. Currently defaults to 1.

     2. max : This refers to the upper limit of the valid k-value range. Currently defaults 1177.

  4. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 2 seconds.

  5. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 2 seconds.

  6. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 120 seconds.

  7. DishVccInitTimeout : This refers to the timeout (in seconds) for the dish vcc initialization. Currently defaults to 180 seconds.

• 8. Variables under deviceServers.subarraynode section

  1. DishIDs : User can set this value to provide the ID’s of dishes present in the deployment. Default is [“SKA001”, “SKA036”, “SKA063”, “SKA100”]

  2. CspAssignResourcesInterfaceURL : Interface version for CSP assign resources command. Currently defaults to “https://schema.skao.int/ska-csp-assignresources/2.0”.

  3. CspScanInterfaceURL : Interface version for CSP scan command. Currently defaults to “https://schema.skao.int/ska-csp-scan/2.0”.

  4. SdpScanInterfaceURL : Interface version for SDP scan command. Currently defaults to “https://schema.skao.int/ska-sdp-scan/0.4”.

  5. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 1.5 seconds.

  6. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 1.5 seconds.

  7. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 110 seconds.

  8. AbortCommandTimeOut : This refers to the timeout for the Subarray ABORTED obsState transition. Once the AbortCommandTimeOut exceeds, SubarrayNode transitions to obsState FAULT. Currently defaults to 130 seconds.

• 1. Variables under deviceServers.sdpsubarrayleafnode section

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 1.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 1.5 seconds.

  3. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 50 seconds.

  4. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

• 10. Variables under deviceServers.sdpmasterleafnode section

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 1.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 1.5 seconds.

  3. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

• 11. Variables under deviceServers.cspmasterleafnode section

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 1.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 1.5 seconds.

  3. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

• 12. Variables under deviceServers.cspsubarrayleafnode section

  1. DelayCadence : This refers to the time difference (in seconds) between each publication of delay values to the delayModel attribute on the CspSubarrayLeafNode. Currently defaults to 10 seconds.

  2. DelayValidityPeriod : This represents the duration (in seconds) for which delay values remain valid after being published. Currently defaults to 20 seconds.

  3. DelayModelTimeInAdvance : This indicates the time in seconds by which delay values need to be available in advance. Currently defaults to 30 seconds.

  4. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 1.5 seconds.

  5. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 1.5 seconds.

  6. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 50 seconds.

  7. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  8. TelmodelSource : This refers to the telmodel source for array layout. Currently defaults to “gitlab://gitlab.com/ska-telescope/ska-telmodel-data?main#tmdata”.

  9. TelmodelPath : This refers to the telmodel path for array layout. Currently defaults to “instrument/ska1_mid/layout/mid-layout.json”.

• 13. Variables under deviceServers.dishleafnode section

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 1.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 1.5 seconds.

  3. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 90 seconds.

  4. MaxTrackTableRetry : This refers to the maximum retries for the programTrackTable write operation. Currently defaults to 3.

  5. TrackTableRetryDuration : This refers to the retry duration (in seconds) for programTrackTable write operation in seconds. Currently defaults to 0.2 seconds.

  6. DishAvailabilityCheckTimeout : This refers to the timeout for the dish availability check during intialisation. This property is for internal use. Currently defaults to 3 seconds.

  7. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

• 14. Variables under deviceServers.dishpointingdevice section

  1. TrackTableUpdateRate : This refers to the rate (in seconds) at which a tracktable is supplied to the DishManager. Currently defaults to 50 seconds.

  2. TrackTableInAdvance : This refers to the time in advance at which programTrackTable needs to be provided. Currently defaults to 7 seconds.

  3. ElevationMaxLimit : This refers to the maximum elevation allowed for observation. Currently defaults to 90.0.

  4. ElevationMinLimit : This refers to the minimum elevation allowed for observation. Currently defaults to 15.0.

  5. AzimuthMaxLimit : This refers to the Maximum value of Azimuth where dish can point. Currently defaults to 270.0.

  6. AzimuthMinLimit : This refers to the Minimum value of Azimuth where dish can point. Currently defaults to -270.0.