1 / 7

Advanced Computing Breakout Session THURSDAY - JUNE 22, 2006 (08:30 - 10:00)

Advanced Computing Breakout Session THURSDAY - JUNE 22, 2006 (08:30 - 10:00) Todd Hutchinson - WSI Chris Harrop – NOAA/GSD Wei Huang – NCAR/SCD Joe Klemp  - NCAR/MMM Gerardo Cisneros - SGI. Pre-Requisites for Petascale Computing. “Computation” is the easy part How do we handle:

dorit
Download Presentation

Advanced Computing Breakout Session THURSDAY - JUNE 22, 2006 (08:30 - 10:00)

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. Advanced Computing Breakout Session THURSDAY - JUNE 22, 2006 (08:30 - 10:00) Todd Hutchinson - WSIChris Harrop – NOAA/GSDWei Huang – NCAR/SCDJoe Klemp - NCAR/MMMGerardo Cisneros - SGI

  2. Pre-Requisites for Petascale Computing • “Computation” is the easy part • How do we handle: • I/O Performance • parallel netCDF, MPI-IO, PHDF, … • Long-term storage • Analysis • Visualization • Feature extraction

  3. Other Petascale Computing Issues • Operations • “Run the same thing over and over with different data” • Or something like that… • Research • Iterative process • Analysis leads to new requirements • Can be difficult to keep a resource busy 24/7 • Capacity vs. Capability • Storage vs. re-run

  4. Other Computing Issues • Dynamic Load Balancing • Many methods • Major software-engineering task, closely coupled with applications • Support for large numbers of chemical species • Adaptive Time-Step • Parallelization of related applications • WPS, wrfpost, (etc.) already done • Others… • Ensemble (workflow) optimization

  5. Other Issues • Ease of use • WPS • Ease of development • Build rework • Registry generation de-hacking • GIS, CF • Coupling • etc…

  6. Other Issues • How do I get my code into WRF? • Process: “do no harm” • Reviewed by WG2 and active contributors • Developers Meetings • Standardized Testing • Realms of responsibility • Not very visible • box.mmm.ucar.edu/wrf/WG2/allreg • Still being fine-tuned based on feedback • Integration support

  7. The Last Slide • Lots to be done… • Software engineering priorities driven by scientific priorities: • Need to prioritize grand challenges vs. everything else (petascale) • Need to prioritize user/developer requirements in general • Which things should we *not* do now? • Action: Publish process for contributed code more visibly

More Related