Bridging Gaps in Simulation Analysis through a General Purpose, Bidirectional Steering Interface with Ascent
Explore the source record for details and available documents.
Engineering topics
Publications and source records attributed to Papka, M E.
Explore the source record for details and available documents.
Scientific simulations can produce enormous amounts of data, making the analysis of results and management of files a difficult task for scientists. The simulation management and analysis system (Smaash) described here is designed to allow scientists to easily capture, store, organize, monitor, and analyze simulation results. The system is automatic, standardized, and secure. Smaash was built using open-source tools and modularized to be independent of the scientific simulation. The web-based front-end allows the scientist to easily interact with the data, and has proved its usefulness in improving the efficiency of a scientific team's workflow. High performance parallel computing allows scientists to solve complex physical problems through computer simulation. However, the massive amounts of data generated and the complex computing environment can create additional complications. A recent review by Ludaescher et al.(2009) describes how scientific workflows can assist scientists in extracting knowledge from these data-intensive operations by automating components within pipelines. Within the fusion community, Klasky et al.(2008) and colleagues have developed a system that handles the storage management, data movement, metadata generation and management, and a means to analyze the results. In response to scientists needs, a simulation management and analysis system (Smaash) was developed at the University of Chicago and Argonne National Laboratory (USA). Smaash provides an integrated way to monitor simulations and analyze computational results; catalog, store, and retrieve simulations; and prepare output for publications. The system is independent of the particular simulation code, accessible from many HPC and browser-based platforms, and built around open-source software tools. Data security and provenance is considered throughout. The analysis components are hidden behind a web-based front end, enabling scientists to focus on their results and not get bogged down by information overload.
Connecting expensive and scarce visual data analysis resources to end-users is a major challenge today. We describe a flexible mechanism for meeting this challenge based on commodity compression technologies for streaming video. The advantages of this approach include simplified application development, access to generic client components for viewing, and simplified incorporation of improved codecs as they become available. In this paper we report newly acquired experimental results for two different applications being developed to exploit this approach and test its merits. One is based on a new plugin for ParaView that adds video streaming cleanly and transparently to existing applications. The other is a custom volume rendering application with new remote capabilities. Using typical datasets under realistic conditions, we find the performance for both is satisfactory.
Collaboration is often an afterthought to a project or development. In this paper we describe and analyze our experiences in developing collaborative technologies, most often involving the sharing of visual information. We have often developed these in a context that required us to retrofit existing analysis applications with collaboration capabilities. This approach, though fruitful, is time-consuming, expensive, and often difficult to re-apply elsewhere - it is just hard to change an existing application. One way to make such an effort easier is to package the collaborative components as a kit that can be leveraged on a case-by-case basis. The fixed interface provided by a well-designed toolkit eases the integration process by providing an unchanging and familiar set of components to deploy. Better still, we find, are approaches that require no modification of applications while providing rich and powerful means for sharing information with collaborators. We discuss three separate and illuminating examples that meet this criterion in different ways: (1) building the collaborative potential into the underlying abstractions on which operating systems are built, (2) building tools that live side-by-side with any application in the context provided by the operating system, or by (3) building information tools that use collaborative modalities to better integrate with our workflow. These are probably not the only options, but they all derive from an approach where collaboration is considered early in the design process and therefore manifests itself deep in the computing infrastructure giving it a wider cast.
Abstract not provided