1 / 13

DOE 2000 PI Retreat Breakout C-1

DOE 2000 PI Retreat Breakout C-1. Deb Agarwal Bruce Mah Ray Bair Carmen Pancerella Steve Karmesin Mary Thompson Rich Lehoucq Brian Toonen Jim Mabon. Enable High-Level Problem Solving Environments. Tools to enable scientists to compose solutions from a set of building blocks

Download Presentation

DOE 2000 PI Retreat Breakout C-1

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. DOE 2000 PI RetreatBreakout C-1 Deb Agarwal Bruce Mah Ray Bair Carmen Pancerella Steve Karmesin Mary Thompson Rich Lehoucq Brian Toonen Jim Mabon

  2. Enable High-Level Problem Solving Environments • Tools to enable scientists to compose solutions from a set of building blocks • Seamless access to remote resources • Enabling infrastructure • Framework standards and interfaces • Implementations of reusable components • Data object conventions • Candidate for SSI effort

  3. Frameworks • Interoperable tools for writing an application • CCA is just a beginning in that direction • Level above libraries • End-user is the application developer • Important to include reference implementations • example application built using the framework tools • allows testing of framework installation • DOE 2000 and SSI

  4. Reusable Components (Continuing DOE 2000) • Separable, hierarchical ensembles • Communication libraries • intrasystem, intersystem, parallel I/O • Numerical libraries • large scale - high performance • Scientific visualization libraries • remote visualization support; shared viz./VR support • Security function libraries • Continue to identify key applications and tools they need (DOE 2000/SSI)

  5. Common Data Objects • Help share data among tools, people, machines • Self-describing data structures, HDF, NetCDF (or) • Standard representations, e.g., XML, LDIF • Data representation conversion capabilities • Move toward unique universal identifiers • Core set of common objects • Objects used frequently in DOE 2000 apps. and tools • Ex: compute resources, certificates, ...

  6. Common Data Objects (cont.) • DOE 2000 work • Standardized objects specific to Collaboratories • Data representation designs • SSI opportunities • Common/self-describing data structures • Collaboration opportunities with other agencies • Facilitate access to and interoperability with digital libraries and archives • Track developments of other projects, e.g., NASA IPG, NSF

  7. Large Data Objects • Data management issues for very large objects • Transport of large data sets and objects • Hiding of (tertiary) storage • Lookup capabilities • DOE2000 foci • Need methods for both small and large objects • SSI may need this capability • Large simulation datasets • Visualization output

  8. Quality of Service • End-to-end performance assurance for applications • Normally thought to be network bandwidth, but also CPU and storage resources • Provide an easy interface for applications to use QoS • Tools so adaptive applications can modify behavior • Debugging and monitoring capabilities • Mostly a new area for DOE 2000 efforts • These capabilities useful to SSI, DOE/DP (ASCI), others

  9. Collaboration Environment • Important to any large, distributed project • Support of interactivity continuum • easy progression... • from low level interaction (MOO, IRC, e-mail) • to mid-level (voice, shared viewers, whiteboard) • to high level (video, app. sharing, screen sharing, shared viz.[SSI]) • Need single login for all DOE 2000/SSI capabilities • Share information between all tools

  10. Collaboration Environment (cont.) • Collaboration agents • activity monitor • contact, filtering, event notification • recording and replay • Support for asynchronous interaction • notebooks and data archives (ongoing) • recording and replay (emerging) • facilitated search/retrieval (emerging) • versioning (new)

  11. Collaboration Environment (cont.) • Approach: low threshold for entry • base functionality with minimal installation • easy installation of additional capabilities • session management and directory services • web-based view of collaborative activities • Remote interaction with resources (instruments, compute resources, databases, compilers) • Project management (SSI addition)

  12. Outreach and Support • Announce available capabilities • provide discovery service (web) • Critical to support initial users • foster component reuse • easy to install, well documented • Enable quick success - does something fast • Open Software approach (when appropriate) • allow users to contribute to the maintenance [Not every innovation has an immediate use. We’re not a large community.]

  13. DOE 2000 Testbed Applications • Build relationships with application efforts • Real use of Collaboratory and/or ACTS tools • establish an initial user base (for feedback) • help validate and steer tool R&D • learn deployment and support requirements • outreach to scientific community • Help connect DOE 2000, ESnet, and other research programs • Complement SSI applications areas

More Related