Release Notes

Details regarding the JIRA tickets that contributed to each PST release are found in the PST Changelog. Important migration information regarding recent PST releases that may is provided below.

1.3.0 to 1.3.1

This is a patch release that fixes compatibility issues between the ska-pst chart and the ska-tango-operator chart (SKB-2347).

1.2.2 to 1.3.0

This minor release introduces new, optional, capabilities to PST:

  • Support for deployment of multiple PST beams into the same Kubernetes namespace, which is required for AA1 and beyond. Refer to Deploy ska-pst with multiple beams in non simulation mode for more information.

  • Support command line overrides to disable the creation of output files, useful in CBF/PST integration environments where the file system provided to PST is too slow to support realtime operations.

  • Introduction of a PST self-test init container that executes configuration, hardware and performance tests on the server onto which PST is deployed. This is disabled by default, refer to Enable ska-pst selftest to check k8s node configuration compatibility for more information.

This release also includes a fix relating to SKB-1045 for packets that were reported as not received (in TANGO attributes) or invalid (in HDF5 statistics files). This was achieved by:

  • Introducing an offset of two Packet Sequence Numbers when a Scan is started.

  • Prevent partially received SMRB blocks from being written to disk when a Scan is stopped.

The Docker images used in ska-pst core deployments (ska-pst-recv, ska-pst-stat, ska-pst-smrb and ska-pst-dsp) have been rationalised into a single ska-pst-core image.

1.2.1 to 1.2.2

This is a patch release that fixes memory leaks in SKA-PST code relating to multiple scans performed in Flow Through Mode (SKB-1017)

1.2.0 to 1.2.1

This is a patch release that fixes some issues found during testing of 1.2.0

  • Fixing of CUDA memory leak issues of the DSPSR code (SKB-1017)

  • Removing dependencies of bitnami in the Helm charts and updating to the latest SKA base Helm charts

  • SEND had multiple small issues that have been resolved

    • If there is issue in generating output statistic files the scan will still be sent to DLM, previously this would cause an issue

    • Fix of a regression introduced in 1.2.0 where the scan length in the output metadata was not being calculated

    • Any scan that fails during processing in SEND will now be moved to the staging/invalid/<flatten_path> directory, where <flatten_path> is <eb_id>_<subsystem>_<scan_id>. This stops SEND from trying to reprocess the scan but no data is lost. When a scan is marked as invalid a warning message will be outputted to the SEND logs.

1.1.2 to 1.2.0

  • Input and Output HDF5 statistics files are now produced by PST for Voltage Recorder and Flow Through processing modes, and made available to the DLM Client for archival in directories

    • input-stats: statistics of the tied-array beam data received from the CBF, generated from short snapshots of data extracted from the Shared Memory Ring Buffer (SMRB)

    • output-stats: statistics of the PST output data streams, generated from the first 100 milliseconds of data in each Voltage Recorder or Flow Through data/weights file pair.

  • Data products produced by the Flow Through processing mode are now prepared for ingest by the DLM Client

  • Container resources in the ska-pst helm chart may now be over-ridden with per container granularity.

  • The container memory requests in the ska-pst helm chart defaults have been increased substantially from 10Gi to 32Gi to accommodate Flow Through mode.

1.1.1 to 1.1.2

  • New attributes added to the PST Beam TANGO device that provide monitoring of the signal processing pipeline performance for Flow Through mode.

  • Migrated PST base OCI images to the SKAO provided builder and runtime versions.

1.0.2 to 1.1.0

  • Migrated to ska-telmodel:1.21.0 and added support for v3.0 of the PST Scan Configuration schema.

  • PST now support using SKA sky_direction for source and coordinates (as per ADR-63).

  • PST no longer transfers output data to the shared SDP CEPH mount.

  • PST now relies on the DLM Client to transfer Voltage Recorder data products to DLM Storage, this integration with DLM has not been verified in this release.

  • PST no longer integrates with the SDP Data Product Dashboard.