Difference between revisions of "SCEC Software"

From SCECpedia
Jump to navigationJump to search
(Redirected page to SCEC Scientific Software)
 
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=== '''SCEC/CME Supported Scientific Software''' ===
+
#redirect [[SCEC Scientific Software]]
  
[[OpenSHA]]
+
SCEC Community Modeling Environment [[CME Project]] researchers have developed a group of inter-related ground motion and seismic hazard modeling software tools that the National Science Foundation SI2 Project describes as a software ecosystem. Funding for this software development work comes from the National Science Foundation (NSF), W. M. Keck Foundation, Pacific Gas and Electric, and other funding sources. The links below provide access to the currently maintained SCEC open-source scientific software distributions.
  
[[CSEP]]
+
[[Image:SCECSoftwareEcosystem.png|right|250px]]
  
[[Broadband Platform]]
+
== Active CME Scientific Software Developments ==
  
[[CVM-H]]
+
*[http://scec.usc.edu/internships/useit/scec-vdo SCEC-VDO]
 +
*[http://www.opensha.org/ OpenSHA]
 +
*[[Broadband Platform]]
 +
*[[CVM-H]]
 +
*[[CVM-S]]
 +
*[[UCVM]]
 +
*[[AWP-ODC]]
 +
*[https://github.com/CMU-Quake/hercules Hercules]
 +
*[[CSEP]]
  
[[AWP-ODC]]
+
== Active CME Scientific Software Platforms ==
 +
SCEC software development staff converts scientific software used by an individual research into scientific software used for community research. [[CME Project]] software developers integrate complex scientific codes together into larger computational systems that we call a [[Computational Platforms]]. Each SCEC computational platform is designed to reliably perform some useful or valuable research calculation. SCEC platforms include dynamic rupture, wave propagation, standard probabilistic seismic hazard calculations, and physics-based wave propagation simulations. In some cases, SCEC provides source code distributions of computational platforms for use by the SCEC community.
  
=== '''SCEC Software Release Policies''' ===
+
*[[CyberShake Project]]
 +
*[[F3DT]]
  
SCEC software engineering group has established standard practices for use when releasing new versions of publicly distributed scientific software. These practices are based on "best practices" for scientific software development established on SCEC's CSEP project and on SCEC's UseIT SCEC-VDO project.
+
== See Also ==
 
+
*[[CME Project]]
Every SCEC/CME project that releases SCEC-developed and SCEC-supported software to the community is expected to provide the following materials before the software is released, unless there is a good reason not to follow these guidelines. Before the SCEC/CME software development group distributes a new version of software, every software project must have the following items:
+
*[[SEISM Project]]
 
+
*[[SEISM2 Project]]
# A public SCECpedia entry that provides and overview of the software project, the capabilities of the software, and a software release history.
+
*[[Geoinformatics Project]]
# A private SCECpedia entry that describes the software development information for the project including design overview, data sources, algorithms used, software language, development environment, run-time environment, and required software stack.
+
*[[CyberShake Project]]
# Copyright statement included in source code.
+
*[[High-F Project]]
# Source code under version control.
+
*[[Main Page]]
# Automated make capability such as makefile or ant script.
+
*[http://www.scec.org SCEC Home Page]
# Issue tracking system (TRAC) site with a trouble ticket system and a connection to source code under version control.
 
# Automated suite of unit tests designed to verify the software was installed correctly and is functional.
 
# Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results.
 
# Automated build and test capability, such as CruiseControl, which will run the acceptance tests without manual interactions.
 
# Release Version assigned using CSEP model of Yr.Mo.x (e.g. v10.8.0) with tags in version control system.
 
# Release Notes, as wiki and pdf, containing the following information:
 
##Software name (or system name) and description of purpose of software
 
##Link to public web page describing project
 
##Description of software capabilities
 
##Description of intended users
 
##Version of current release
 
##Overview of changes including new capabilities of current release
 
##Software support email list
 
##Contact for Responsible scientists
 
##Contact for Responsible Software Engineer
 
##How to report software problem or request features
 
# User documentation, as wiki and pdf, including:
 
## Computer User Guide to installing, building, verifying, and operating software
 
## Scientific User Guide to using software, running reference problem, and interpreting results
 

Latest revision as of 04:29, 12 September 2015

SCEC Community Modeling Environment CME Project researchers have developed a group of inter-related ground motion and seismic hazard modeling software tools that the National Science Foundation SI2 Project describes as a software ecosystem. Funding for this software development work comes from the National Science Foundation (NSF), W. M. Keck Foundation, Pacific Gas and Electric, and other funding sources. The links below provide access to the currently maintained SCEC open-source scientific software distributions.

SCECSoftwareEcosystem.png

Active CME Scientific Software Developments

Active CME Scientific Software Platforms

SCEC software development staff converts scientific software used by an individual research into scientific software used for community research. CME Project software developers integrate complex scientific codes together into larger computational systems that we call a Computational Platforms. Each SCEC computational platform is designed to reliably perform some useful or valuable research calculation. SCEC platforms include dynamic rupture, wave propagation, standard probabilistic seismic hazard calculations, and physics-based wave propagation simulations. In some cases, SCEC provides source code distributions of computational platforms for use by the SCEC community.

See Also