Skip to main content
eScholarship
Open Access Publications from the University of California

Scholarly Works (2 results)

  • Article
LBL Publications (2002)
In 1999, the PITAC Report recommended the creation of a national library of certified domain-specific software in order to reduce the labor required for software development, testing and evolution (some of those recommendations were later implemented by the Networking and Information Technology Research and Development Program. From interactions with many computational scientists and industry we have realized that ACTS has the potential of becoming a major player in such an activity. Computer vendors and a great part of the scientific computing community are already familiar with at least a couple of the ACTS tools. The implementation of the peer-reviewed certification will push the frontiers of the tools forward, and the tools or subsets of the tools will be eventually integrated in vendor-supported software libraries.We seek to work with tool developers and leading computational scientists in defining the criteria to be used in the certification process. In this paper we present an initial set of parameters to carry out such a process.
    Cover page: The ACTS collection robust and high-performance tools for scientific computing: Guidelines for tool inclusion and retirement
    • Article
    Lawrence Berkeley National Laboratory (2006)

    In the next five years, the DOE expects to build systems that approach a petaflop in scale. In the near term (two years), DOE will have several near-petaflops systems that are 10 percent to 25 percent of a peraflop-scale system. A common feature of these precursors to petaflop systems (such as the Cray XT3 or the IBM BlueGene/L) is that they rely on an unprecedented degree of concurrency, which puts stress on every aspect of HPC system design. Such complex systems will likely break current best practices for fault resilience, I/O scaling, and debugging, and even raise fundamental questions about languages and application programming models. It is important that potential problems are anticipated far enough in advance that they can be addressed in time to prepare the way for petaflop-scale systems. This report considers the following four questions: (1) What software is on a critical path to make the systems work? (2) What are the strengths/weaknesses of the vendors and of existing vendor solutions? (3) What are the local strengths at the labs? (4) Who are other key players who will play a role and can help?

      Cover page: Software Roadmap to Plug and Play Petaflop/s
      Top