1 / 10

DOE2000 Directions - M2 group

DOE2000 Directions - M2 group. Members Larry Rahn, SNL Larry Allard, ORNL George Chin, PNNL Terry Disz, ANL Debbie Gracio, PNNL Jim Kohl, ORNL Dan Quinlan, LLNL John Reynders, LANL Bill Saphir, LBNL Steve Wright, ANL. DOE2000 Directions - M2 group. Process

misty
Download Presentation

DOE2000 Directions - M2 group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DOE2000 Directions - M2 group • Members • Larry Rahn, SNL Larry Allard, ORNL • George Chin, PNNL Terry Disz, ANL • Debbie Gracio, PNNL Jim Kohl, ORNL • Dan Quinlan, LLNL John Reynders, LANL • Bill Saphir, LBNL Steve Wright, ANL

  2. DOE2000 Directions - M2 group • Process • First we discussed (for 8 hours...) • Program structure, technical goals • Challenges • Current program issues • DOE 2000 added value • Generally exchanged information, philosophies • Then we finally answered A, B, & C

  3. High-level priorities • Promote interoperability/component specifications (e.g., CCA) • Preserve unique DOE2k approach to complement SSI • Identify new opportunities to exploit our approach to software development

  4. Priorities for program structure • Projects must be well defined • Finite-time development cycle • Follow-on funding for maintenance of successful projects • Develop process for distributing DOE software • Open source (www.opensource.org/osd.html) • Uniform practice for DOE2k

  5. DOE 2k project selection criteria • Enhance software tools to be: • Interoperable • Portable • Reusable • Multi-application • Highly leveragable • High performance on parallel architecture

  6. Priorities for collaboratory projects • Close interaction of pilot projects with tool development to address needs • Electronic notebook critical component • Pilots need to incorporate more tools • New mechanisms for pilot-tool collab. • Document pilot tool integration to guide development of new collaboratories

  7. New application opportunities - 1 • Grid generation tools • AMR • Wide area group collaboration • Collaborative Visualization • Collaborative Problem Solving Environments • Data management and mining

  8. New application opportunities -2 • New numerical methods -> performance • Uncertainty analysis- • Stochastic optimization, • Sensitivity analysis, automatic diff. • Also possible • Visualization tools • Eigen solvers

  9. Coordinating with other agencies • Technical activities • NASA Ames - • Grid generation tools • Astrobiology Inst. -> Collabative tool devel. • NASA, DARPA, NSF - • Post Doc(ument) for collaborative document generation NASA • PACI partners -Grids, integration frameworks • Education and lab involvement

  10. Coordinating with other agencies • Technical activities (cont’d) • NIH - Telemicroscopy project • NSF - Meta NEOS (Globus, optimization) • NSF - SSI program in Human-Comp. Inter. • Collaboration mechanisms • Shared tools (NASA Grid from CAD) • Site visits for awareness • PACI partners alliance meetings

More Related