 News |
FAQ
|
| Search
|
Home
|
| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
|
| Version 1.9 Build 803 |
|
There are three phases in redesigning and reimplementing Observe:
Considering the nature of observe, the language of choice is Java. Why Java?
The following list is a "back-of-the-envelope" targets list that would be refined after the design work. Time estimates indicate the relative amount of work (rather than the actual time). The time required to implement the GUI is likely to be independent of implementation (Java, X11, Tcl/Tk, or GlishTk).
Testing individual components and programs will follow the AIPS++ model. As we finish parts of the project, we prepare test-cases with known results. At regular intervals the test-cases are run and compared with expected results. If a test fails we can track it down before it becomes a bug report. Also, we can run the test-cases after any changes to ensure no unforeseen problems have occurred. Testing the GUI is more labor intensive and will require interactive testing by NRAO staff members.
| VLA Observe - Targets |
| Phase 1 - Design - deliverable (2 weeks) |
| rudimentary design of current Observe |
| redesign Observe |
| Phase 2 - Foundation (17 weeks) |
| ASCII Text to Observe file - deliverable (9 weeks) |
| conversion into Java |
| parser |
| user defined |
| observe file |
| interface with AIPS++ Measures |
| scheduling routines |
| frequency checking |
| output routines |
| unit testing |
| Reports - deliverables(4 weeks) |
| analysts |
| scheduling |
| frequency |
| time-on-source |
| summary |
| unit testing |
| Databases - NRAO/user (3 weeks) |
| frequency setups - deliverable |
| calibrator - deliverable |
| source - deliverable |
| position |
| orbital elements |
| interpolated from table |
| Integration into a scheduler - deliverable(1 week) |
| Phase 3 - Interactive Interface (20 weeks) |
| Scheduler GUI (10 weeks) |
| screen layouts - deliverable |
| source catalog - deliverable |
| frequency/correlator setups - deliverable |
| scan editor - deliverable |
| visual loser - deliverable |
| LO calculator |
| band/interference plots |
| Doppler tracking |
| observe file viewer - deliverable |
| scan contraction/expansion |
| starting conditions - deliverable |
| editing schemes |
| User Testing (4 weeks) |
| Planning Tools - deliverables (2 weeks) |
| uptime |
| uv-coverage |
| az-el plots |
| calibrator flux history |
| Distribution - deliverable (1 week) |
| Documentation (4 week) |
| programmer - deliverable |
| user - deliverable |
| tutorial |
| on-line help |
| Phase 4 - Futures (?) |
| suggested schedule |
| time range, source, frequency, pick calibrators, etc... |
| optimal scheduling |
| incorporate VLA plan |