Difference between revisions of "CSEP1 Status"
| Line 6: | Line 6: | ||
; Guiding Principals | ; Guiding Principals | ||
| + | # Controlled Environment | ||
# Transparency | # Transparency | ||
| + | # Comparability | ||
# Reproducibility | # Reproducibility | ||
| − | |||
The locks are used to prevent data contamination, and to prevent overwriting data by a different process. This is required because CSEP uses the same directory for all forecast models before moving forecast files to archive directories | The locks are used to prevent data contamination, and to prevent overwriting data by a different process. This is required because CSEP uses the same directory for all forecast models before moving forecast files to archive directories | ||
Revision as of 00:22, 16 March 2018
Contents
Introduction
Retrospective experiments of earthquake forecasts represent an important aspect of the CSEP software infrastructure. They provide significant insight into the performance of earthquake forecasting models and allow scientists to evaluate the performance of forecasts on historic earthquake sequences. The CSEP1 system is designed to support retrospective forecast experiments in addition to prospective forecasting. CSEP operates entirely in serial; meaning that both retrospective and prospective processing capabilities must happen sequentially. This sequential behavior is enforced within CSEP using locks that are placed on active directories during computation. While the serial nature of the system is not general, working around the CSEPLocks require non-elegant hacks. This document explores the possibility of repurposing a "stand-alone" reprocessing tool that can operate concurrently. The CSEP tool must not violate any of the guiding principals of CSEP.
- Guiding Principals
- Controlled Environment
- Transparency
- Comparability
- Reproducibility
The locks are used to prevent data contamination, and to prevent overwriting data by a different process. This is required because CSEP uses the same directory for all forecast models before moving forecast files to archive directories
