McIDAS-V Requirements for October 2007 McIDAS Users' Group Meeting

Below is a list of requirements that we feel are necessary to the current McIDAS-V for the October McIDAS Users’ Group Meeting. These requirements need to initially be completed by June 2007. This will allow time for testing and programmer/tester iteration. Full completion of these requirements in July 2007 provides ample time for the McIDAS User Services group to put together the needed user documentation and prepare the user hands-on training session.

Items 1-4 are necessary for the MUG Meeting; item 5 would be a nice addition, but can be the next item tackled if time is short.

1. The McIDAS-V GUI must be updated from the current IDV GUI.
   1. The current Mc-V dashboard shall be updated to utilize the VisAD and IDV libraries , but shall resemble the current McIDAS-X GUI. {Be sure to use DAY= and TIME= for images, in order to utilize the archive.}
   2. The data choosers shall be updated for quick access to commonly used data features, such as wizards, buttons, memory of last used options,...
   3. The default configuration settings shall be updated as needed (data display onto map or in data's projection?, ...).
   4. The McIDAS-V GUI shall be easily configured by users, including being able to add and remove different data types and data from different servers.
   5. Publish GUI standards for use or reference by our programmers and other users.
2. McIDAS-V must be able to bridge with current McIDAS-X.
   1. McIDAS-V must send and receive text to/from McIDAS-X.
   2. McIDAS-V must visualize navigated graphics and images from McIDAS-X.
   3. McIDAS-V must interpret the ADDE request made by McIDAS-X and subsequently visualize the data without McIDAS-X.
   4. McIDAS-V must display non-navigated displays (e.g. meteorogram) within a separate image viewer.
   5. McIDAS-V must handle both time-based loops and frame-based loops.
   6. The functionality of interactive McIDAS-X commands (e.g. EB) shall be available in McIDAS-V. {needs to either work through the bridge or the functionality needs to be added to McIDAS-V}
   7. McIDAS-V needs an indicator to know if there is a problem with the McIDAS-X session.
3. The installation and configuration of McIDAS-V and the McIDAS-X listener must be easy.
   1. The installation and configuration of McIDAS-V and the McIDAS-X listener must work on all platforms supported by the MUG.
   2. Users should be given an option of installing from binary (the default) or compiling from source.
   3. The installation should be simple with logical defaults.
4. The HYDRA integration to McIDAS-V must be completed.
5. McIDAS-V, without the bridge, must access and output other types of data already available in McIDAS-X.
   1. Display local and remote image datasets, including old satellite imagery
   2. Plot and contour local and remote grid datasets
   3. Plot and contour local and remote point datasets
   4. Save the digital data file(s) generated in a, b, or c