 News |
FAQ
|
| Search
|
Home
|
| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
|
| Version 1.9 Build 803 |
|
During this development cycle I have fulfilled several coordination roles as Deputy Project Manager. These have included the coordination of development in synthesis, parallelization and NRAO visualization efforts. I have also contributed to the coordination of development planning activities for v1.5 and v1.6, and the drafting of the development plan for each of these cycles. I have continued as technical leader for AIPS++ during this period, and have contributed to systems issues as part of that role. This has included direct involvement in release preparation and associated patch application and testing. I have maintained a direct involvement in code generation, defect correction and user support, particularly in the area of MS infrastructure, calibration capabilities and parallelization infrastructure. Activities in these areas have included enhanced polarization calibration facilities, the creation of higher-level synthesis applications and the unification of existing MS access code. I have been involved in a number of public outreach activities for AIPS++, including working directly with user groups, and have prepared and given presentations on AIPS++.
David King
I have been working on DisplayData classes to be used in things like msplot for display and editing of MS data. To that end, I have been studying the workings and interface of many parts of the Display and general aips++ library: canvases, DDs, glish interface, GUI elements, CoordSystems, Images, MSs, Tables, access/iteration classes, and basic data structures (probably over 150 major classes in all).
I am also trying to learn the science as fast as I can (it is really essential to understanding the form of the problem). I have a lot of catching up to do, but feel I am making good progress, and am enjoying the challenge.
I am starting with the Raster (TVFLG-like) DD, and have some basic user interface mapped out and working through to the viewer. The basic structure of the DD is also clear: it will retrieve data from a single MS using VisIter and related access classes, and present it to the user as a five-axis hypercube (Time, Baseline, Sp. Window, channel, and polarization). Usually time, along with baseline or channel, will be the current 2D slice viewed, other axes being controlled through sliders/animators. In principle, any of the axes may be set as display axes; sky Images currently have this flexibility in the viewer. I need to share as much of that structure as possible.
Very recently I have created a test program for iterating MSs, and am gathering useful information on access efficiencies in different modes, as well as learning how to operate the iterators. I am currently working on extracting ranges, creating Coordinates and an Image, to test how quickly such a lattice can be built and accessed. These should comprise the major data structures for display in the DD; it remains to be seen how much of the data (between the Matrix currently displayed and the entire MS selection) should be cached in an Image.
Other details I'm thinking about: time and channel averaging, editing interface elements, data structures to go back from GUI editing events to the flag data, combining, ordering and removing degenerate axes in the ui, coordinate labeling in various cases and forms. Fortunately, I believe a simple framework that actually displays some uv data can be created fairly soon, and will provide concrete terms for addressing these issues afterward. I am staying in touch with Ralph to integrate the DDs into msplot, and to make use of his experience.