Things To Do
The following is a partial list of things that need to be done to
the GUI.
Improve Real-Time Monitoring
The real-time monitoring system needs some refinements.
- Currently it has a probably-wrong way of calculating what it
calls "summary" plots. Summaries should be computed on the
DiFX host using the proper means for amplitude and phase
individually.
- Should be able to compute delay rates, SNR, etc.
- Plots should be broken up by "scan" - currently data are
combined between scans, which is completely wrong (so real-time
monitoring only makes sense for jobs that contain a single
scan).
- Real-time monitoring should work for more than one job at a
time (probably involves changes to DiFX software).
- "Quit at 80%" problem needs to be fixed (also DiFX
software...)
Automated Run Scheme
- Jobs should pick data sources and processors that make sense
for the job, resources available, etc.
- User should be able to select and run a number of jobs at once
(they'd run however the user set them up to run, or with
sensible choices for data source and processors - see bullet #1
- if the user didn't bother doing that).
- Have GUI learn the most efficient way to use the existing DiFX
cluster??
Secure Communications
TCP connections between the GUI and guiServer are not
secure, thus they (in general) can't work over anything but a
secure LAN. Not as easy as it sounds to fix - there are many
TCP connections made.
Other
- GUI does not recognize CalcServer not running (common problem)
gracefully. Should do so, allow user to start it, etc.
- How well do multiple GUI's running at once work (relaying of
broadcast messages, etc)? Broadcast message collection
should probably be done once, and distributed to all connected
GUI's (currently I think it is done once for each).
- The database stuff needs to be modernized - hasn't been
touched in over a year, might not work.
- Mark 5 directory stuff is spotty - sometimes it works,
sometimes it doesn't.