7.2. Known
issues and outstanding items
-
Square root encoding of the Visibility Flagging Fraction. Computing a
square root in an FPGA requires a lookup table which is resource
intensive. SDP needs to determine what precision is required (and
where) in the flagging fraction to see if alternative encoding of the
flagging fraction is feasible.
-
How FTP is implemented for transferring the PSS and PST data from CSP
to SDP still needs to be discussed, in particular with regards to SDP
hosting FTP servers (which is a risk for SDP).
-
The VLBI data carriage still needs to be confirmed.
-
The lack of support in SPEAD2 to the ‘0’ (zero) format code. The
Python SPEAD2 bindings (referred to in Section 5.1.1.1) do not support
the ’0’ format code, according to the documentation:
https://spead2.readthedocs.io/en/latest/py-protocol.html
(See point 4 in the list). [See par 5.1.1.4 Table 3]
-
Specifying the ItemDescriptorType as a numpy data type (dtype)
should solve this issue. Could add the dtype for each Item
Descriptor in the table.
-
The mapping of logical entities to PSRFITS keyword and actual layout
of the PSRFITS file and tables.
-
The bandwidth requirements from the baseline design and L1s Rev 10 vs
the costed ingest capacity for SDP.