Difference between revisions of "Product Backlog - William"

From SCECpedia
Jump to navigationJump to search
(Created page with "William Savran's Project/Product Backlog == Project/Product Backlog == * Publicize CSEP glossary of terms * Build CSEP from source code and create distributable image == Rel...")
 
 
(101 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
William Savran's Project/Product Backlog
 
William Savran's Project/Product Backlog
  
== Project/Product Backlog ==
+
== Product Backlog ==
* Publicize CSEP glossary of terms
+
# research and develop new techniques for the rigorous statistical evaluation of stochastic event sets
* Build CSEP from source code and create distributable image
+
# reprocess missing one-day forecasts/evaluations identified from csep_db
 +
# provide open source codes for CSEP1 evaluations to begin modularizing current CSEP1 codebase
 +
# create archived csep1 data set containing all data and meta-data from csep operational servers and provide to the community
 +
# run 1-year u3etas and no-faultsETAS simulations from start of >Mw 2.5 catalog (~1985) until current day to provide data set for applying csep2 evaluations on stochastic event sets
 +
# prototype tests of forecast of finite-ruptures, for example, in the ground motion domain
 +
# develop a protocol to accept external forecasts for CSEP testing
 +
# develop plan to ensure the continued prospective testing of csep1 models
 +
# develop blueprint to describe how to implement current on-demand CSEP 1 processing and reprocessing.
 +
# write data management plan for the csep2 ecosystem.
 +
# implement restAPI to provide access to csep2 data archives.
  
 
== Related Entries ==
 
== Related Entries ==
 
*[[CME Software Staff]]
 
*[[CME Software Staff]]
 
*[[CME Project]]
 
*[[CME Project]]

Latest revision as of 20:56, 11 January 2019

William Savran's Project/Product Backlog

Product Backlog

  1. research and develop new techniques for the rigorous statistical evaluation of stochastic event sets
  2. reprocess missing one-day forecasts/evaluations identified from csep_db
  3. provide open source codes for CSEP1 evaluations to begin modularizing current CSEP1 codebase
  4. create archived csep1 data set containing all data and meta-data from csep operational servers and provide to the community
  5. run 1-year u3etas and no-faultsETAS simulations from start of >Mw 2.5 catalog (~1985) until current day to provide data set for applying csep2 evaluations on stochastic event sets
  6. prototype tests of forecast of finite-ruptures, for example, in the ground motion domain
  7. develop a protocol to accept external forecasts for CSEP testing
  8. develop plan to ensure the continued prospective testing of csep1 models
  9. develop blueprint to describe how to implement current on-demand CSEP 1 processing and reprocessing.
  10. write data management plan for the csep2 ecosystem.
  11. implement restAPI to provide access to csep2 data archives.

Related Entries