- Antenna Control. A P.C. version of the PMAC motion controller will control
the antenna, for two reasons:
- The P.C. version of the PMAC gives better tuning and diagnostics
capability, since the PC has a higher bandwidth connection to the PMAC
memory.
- We are short on VME slots in the data system chassis, and don't want to
use 3-4 slots for a motion controller, if not absolutely necessary.
Implication: We need to enhance existing real-time antenna control software
to communicate over a serial port, as well as to the VME version of the PMAC.
(In contrast to the C-Band and TASS implementation, where we used a VME
version of the controller).
- Data Format. We should generate DORADE format calibrated tapes, that do
not require post-processing to be viewed by SOLO or ingested by ZEB.
- Calibration. We will generate the data with a "default" calibration, so
that it can be immediately perused by project scientists. The data format will
be written to provide enough information to apply other calibrations in a
post-processing stage, if necessary.
Implication: the signal processor should use a calibration curve, rather
than a simple straight line approximation to convert power counts to DBZ.
- Playback capability. For display development and communication line
testing, the real-time data system should be able to replay "field" tapes and
produce a base-data stream on ethernet that is indistinquishable from the
base-data produced by the running radar.
- Data Quality Assurance. To avoid having to physically transport data tapes
to an RDP facility, we should provide RDP software on the data acquisition
workstations. (At the minimum, SOLO, and probably ZEB, as well).
Implication: Need extra disk space (1 gigabyte?) to install software and
buffer in tape data onto disk.