Editor's Note: Use of Unidata's Integrated Data Viewer, aka IDV, is growing. When we learned that a long-time community member who's used another visualization and analysis tool for many years was migrating to the IDV, we wondered why and asked him to provide a write-up about the topic. Dave Dempsey's (SFSU) explanation is below.
by Dave Dempsey, San Francisco State University
Community Members Contribute to IDV Development
"The IDV developers worked with us to fix some Mac-specific bugs in a beta release that came out in time for us to use before the semester ended. Their responsiveness was welcome. While dealing with the bugs detracted from the IDV learning experience, it made us feel like contributing members of the community of IDV developers. "
--Dave Dempsey, SFSU |
|
We decided last year to begin migrating to the IDV for classroom use, based on a long-awaited convergence between the development of the IDV and our ability to use it.
In the early 1990s, we adopted WXP for classroom use, when it was supported by Unidata and the IDV wasn't yet on the radar screen. WXP seemed best suited to the needs of our program at the time. All of the available packages were command-line driven; a GUI wasn't an option.
Command line interfaces are not particularly easy to use. To make WXP programs easier to use for our curricular purposes, I began developing Unix scripts that simplified the WXP command-line interface. By the time GUI interfaces became available for the competing weather-graphics software packages, I'd written (and debugged!) probably 60,000 lines of code and developed a required meteorology major's class that in part taught students how to use the scripts (along with WXP itself).
In 1995 I got a small SFSU grant to set up what I dubbed the California Regional Weather Server (CRWS) (http://virga.sfsu.edu). The idea was to generate GIF versions of some of the maps and images that I'd been developing for in-house curricular use and make them accessible to the general public, updating them automatically via cron jobs. There weren't a lot of weather maps and images specific to California available at that time, so I hoped to help fill that niche. WXP made this possible, and it remains essential to the CRWS's ongoing success.
Classroom use is another story. Many of today’s students have grown up with the Web and don't have much patience for command-line interfaces. It's been just a matter of time before we switched to software with a GUI. However, to switch to the Java-based IDV, several conditions had to be met:
- We needed to acquire enough computers capable of running not only the IDV but also the variety of other software we use in the classroom.
- The IDV had to become both comprehensively and computationally efficient enough for classroom use.
- We had to learn how to use the IDV well enough to incorporate it into our teaching.
- We had to have confidence that Unidata would develop and support the IDV over the long term.
In 2002 we were able to buy 18 laptop computers to equip a 36-seat classroom that we renovated to permit any combination of traditional lecturing, networked computing, and small-group collaborative work. For historical reasons most of our Department of Geosciences faculty (2/3 geologists, 1/3 meteorologists and oceanographers) have used Apple Macs, and Macs running Apple's Unix-based OS X proved friendly enough for students more familiar with Windows PCs, so we bought then state-of-the-art, 15", 800 MHz, Mac Titanium G4 laptops.
By early 2005, Apple finally had an implementation of Java that could support nearly all of the IDV's features. In summer 2005, we upgraded the memory in our laptops to 1GB of RAM, which is plenty for the IDV. Moore's Law means that our laptops are now about 6-8 times slower than machines available today, but the IDV's efficiency had improved sufficiently that our laptops were just fast enough to make using the it in our classroom feasible.
In summer 2005, I attended an IDV training workshop at Unidata. Without that training, I don't think I could have taught our students and my colleagues to use the IDV adequately. With the training, I felt I could. Moreover, although I'd known something about the IDV beforehand, I hadn't fully appreciated how much more it had become than just a weather graphics package with a GUI.
For example, the IDV can access data residing not only on the local machine but also on remote servers, whereas WXP can access only locally available data. This means that students can use the IDV to complete part of their class work at home if need be, something that is much harder to do with WXP.
The IDV has some analysis and display capabilities that WXP lacks, some of which are spectacular. The IDV's ability to create (and animate and rotate) 3-D visualizations of model data, radar data, aircraft track data, and the like is particularly eye grabbing. It can display GIS shapefiles, which opens up a vast world of GIS-like possibilities. The User's Guide reveals a number of other distinctive capabilities.
The IDV has its shortcomings, of course. However, Unidata has dedicated staff to the IDV's ongoing development, and because Unidata and the IDV's developers are sensitive to the needs and concerns of academic users like us, many of the IDV's remaining shortcomings will likely be addressed. To me this makes a shift to the IDV feel like a safe bet over the long haul.
Emboldened by that Unidata training workshop, I decided to begin our switch to the IDV. We were finally ready to make the leap.
Last fall I modified a required majors course, in which I used to teach students to use WXP, to use the IDV instead. I relied heavily on Unidata's training workshop materials as well as the Users Guide. I'd found the IDV's learning curve a bit steep in the beginning (though no more so than other packages), but the students seemed to scale it more easily than I, which was a bit disconcerting!
We discovered some Mac-specific and other bugs, but the IDV developers worked with us to fix them quickly. Dealing with those bugs detracted from the IDV learning experience but it also made us feel like contributing members of the community of IDV developers. Don and Jeff paid us a half-day site visit during their attendance at the annual AGU meeting in San Francisco last December, and they boosted our understanding of the IDV and noted carefully our wish- list of features and alternative user interface designs. Their responsiveness was welcome.
It'll be a while before we build up the experience and the body of course-specific IDV "bundles" needed to integrate the IDV into our curriculum more fully and effectively, but we're in for the long haul and that will eventually happen.
Meanwhile, I just love making animated, global 3-D jet stream visualizations with a 3-D temperature surface plotted below it. It does just what I'd hoped it would do when I wrote a "Use Case" for it back in the early stages of the IDV's development
|