SCIENCE TEAM III GRAND CHALLENGE INVESTIGATOR MILESTONES
Interoperability Based Environment for Adaptive Meshes (IBEAM) with Applications to Radiation-Hydrodynamic Models of Gamma-Ray Bursts
Paul Saylor, University of Illinois at Urbana-Champaign
| Num | Label | Milestone | Expected | Certified |
|---|---|---|---|---|
| 1. | A | Complete Software Engineering Plan. The IBEAM collaboration and GSFC inhouse PARAMESH team will negotiate changes to PARAMESH and IBEAM requirements for IBEAM Framework v1.0. The IBEAM team will also engage the GSFC viz team to identify areas of mutual interest in the area of scientific visualization. The IBEAM team will also deliver the following documents for this milestone: 1) The Software Engineering Plan for IBEAM, 2) The IBEAM Framework Configuration Management Plan, and 3) The IBEAM Quality Assurance Plan. |
03/02 | 06/02 |
| 2. | E Perf. revs. |
Code baseline completed. Delivery of IBEAM v1.0 and Documentation. This will include the delivery of generation I linear system solver (BiCGSTAB) module and the relativistic hydrodynamics module. Scientific metric will be the simulation of a relativistic hydrodynamic blastwave interacting with external inhomogenieties using AMR. Performance metric will be achievement of 15% of theoretical peak speed of parallel platform provided by NASA. The IBEAM team will also deliver the following documentation: 1) An initial draft of the IBEAM Requirements Document (.pdf), which will specify an interface for modules to plug-in to the IBEAM framework, and 2) An initial draft of the IBEAM Design Document describing the design of IBEAM. Documented source code will be made publicly available via the Web (ITAR regulations apply). |
06/02 | 04/03 |
| 3. | O1 | Linux cluster installed. The IBEAM Team will construct a Beowulf cluster and deploy IBEAM and the IBEAM modules on this cluster. This cluster will serve a two-fold purpose. First, the cluster will serve as a development testbed for IBEAM and IBEAM module programmers, thus relieving the NASA parallel platform of routine development work that would tie up production queues. Second, the Beowulf system will serve as a production environment that will allow us to explore a wide range of GRB models (at low resolution) quickly and at low cost.Once interesting parameter values and initial model configurations are determined, the production runs will move to the NASA-supplied parallel architecture.Furthermore, this cluster will serve as a teaching tool for our graduate students, allowing them to learn the rudiments of parallel programming in a lower cost environment. Finally, performance tuning on this cluster will allow us to make optimal use of any larger Beowulf clusters that NASA may make available to us during the course of this cooperative agreement. |
07/02 | 08/03 |
| 4. | B | First Annual Report delivered. Submit FY02 Annual Report to CT via the Web. |
08/02 | 08/03 |
| 5. | H | Design policy for interoperability and community delivery agreed on. IBEAM v1.0 will allow interoperability of the relativistic hydrocode module and at least one other hydrodynamics module. The codes will perform simulations of an expanding relativistic Sedov-Taylor blastwave at 512x512 resolution. We will also develop and advertise throughout the community a Web-based forum designed to solicit suggestions for a community standard interface for IBEAM modules. We will also work with NASA to solicit plug-in proposals for IBEAM from this community. The IBEAM team will also supply an updated IBEAM Requirements Document and an updated IBEAM Design Document (.pdf) which describe the version of IBEAM delivered in milestone E. The IBEAM team will also provide an initial draft of the IBEAM test plan and IBEAM testing procedures (.pdf).< |
09/02 | 12/03 |
| 6. | F | First code improvement completed. Delivery of multigroup radiation diffusion and multigroup Boltzmann transport modules, delivery of generation II linear system solver module. Documented source code will be made publicly available via the Web (ITAR regulations apply). |
07/03 | 01/04 |
| 7. | C | Second Annual Report delivered. Submit FY03 Annual Report to CT via the Web. |
08/03 | 02/04 |
| 8. | I | Interoperability prototype from Milestone H tested with improved codes. IBEAM will demonstrate full radiation-hydrodynamic interoperability with at least two radiation transport code modules (one multigroup flux-limited diffusion module and one Boltzmann transport module). The scientific metric will be the conduct of GRB fireball model simulations with full radiation hydrodynamics at 256x256 spatial resolution. These simulations will be compared with NASA space science data (GRB light curve and spectral data) to constrain models for the bursts. Our performance metric will be to achieve 10% theoretical peak speed of NASA parallel platform on full radiation hydro simulations. Note that since we are unaware of the nature of the parallel platform at this time, and given the larger amount of global communication needed for the linear system algorithms arising from the implicit scheme, we have set a lower goal for the attained fraction of theoretical peak speed. When information about the parallel architecture becomes available we may wish to renegotiate a higher performance metric for this milestone. Additionally, we will work with plug-in teams selected by NASA to achieve interoperability of any plug-in modules that exist by this date. |
09/03 | 01/05 |
| 9. | G | Second code improvement completed. Scientific metric: full radiation-hydrodynamic simulations of GRB's carried out with IBEAM on extensive series of initial models at 2x spatial resolution or 2x angular resolution. Performance metric: achievement of 10% of theoretical peak speed of machine. As with milestone F, we may wish to renegotiate a higher performance milestone once the details of the available parallel architecture are known. Documented source code will be made publicly available via the Web (ITAR regulations apply). |
04/04 | 02/05 |
| 10. | J | Full interoperability demonstrated using improved codes. Delivery of IBEAM 2.0 using dynamic grid allocation with PARAMESH 2.x employed as a library. The following documentation for this version of IBEAM will be supplied by the IBEAM team: 1) An updated IBEAM Requirements Document, 2) An updated IBEAM Design Document, 3) An Updated IBEAM Test Plan, and 4) An Initial User's Guide. We will work with the plug-in teams to integrate any new plug-in modules that exist at this time. |
06/04 | 05/05 |
| 11. | D&K | Customer delivery accomplished. Final Report delivered to CT via the Web. Delivery of final version of IBEAM with full interoperability of all modules (including plug-ins). The Final Report will contain the results of the interoperability tests. The IBEAM team will supply the following documentation to reflect IBEAM 2.0 as delivered in milestone J: 1) an updated IBEAM Requirements Document, 2) an IBEAM Design and Maintenance Document, 3) an Updated IBEAM Test Plan, and 4) an updated User's Guide. Documented source code will be made publicly available via the Web (ITAR regulations apply). |
12/04 | 05/06 |
+ Home
