...
The output visibility modes of MWAX using 128 tiles that run real-time on the as-built MWAX hardware configuration are available at this page: MWAX Correlator Modes (128T)
...
The figure below shows the processing stages and data flows within the MWAX correlator FX Engine process.
The FX Engine treats individual 8 second sub-observations as independent work units. Most of its mode settings are able to change on-the-fly from one sub-observation to the next. It operates on 50 ms units of input data, i.e. a total of 160 blocks over each 8 second sub-observation. An additional block of metadata (of the same size as a 50 ms data block) is prepended to the data blocks, making a total of 161 blocks per sub-observation. At the start of each new sub-observation, the metadata block is parsed to configure the operating parameters for the following 160 data blocks.
...
The data capture process, running on each MWAX Server, reads visibility data off the output PSRDADA ring buffer and writes the data into FITS format. The data capture process breaks up large visibility sets into files of up to approximately 5 10 GB each, in order to optimize data transfer speeds while keeping the individual visibility file sizes manageable. The FITS files are written onto a separate partition on the MWAX Server disk storage.
...
mwax mover iterates through each file in the queue, firstly creating computes a checksum, creates a record in the MWA metadata database for each file and secondly attempting then attempts to transfer them to an MWAcache Server at the Curtin 206 data centre via the MRO-to-Perth 100 Gbps link. The transfer is performed using xrootd, a high performance, reliable and scalable file transfer protocol. In the event that the 100 Gbps link to the Curtin 206 data centre is down, or there are issues with the MWAcache Servers, the mwax_mover process will requeue the files and attempt to transfer them when the systems or link are back online.
...