Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Current Items == | == Current Items == | ||
*Modify CyberShake to work on RSQSim ruptures | *Modify CyberShake to work on RSQSim ruptures | ||
| − | |||
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files | **Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files | ||
*CyberShake training | *CyberShake training | ||
*Update CyberShake study wiki pages to point to SQLite files | *Update CyberShake study wiki pages to point to SQLite files | ||
| + | *Create wiki page for CyberShake RSQSim, and upload sample seismograms | ||
== Project Backlog == | == Project Backlog == | ||
| + | *Run CyberShake post-processing on RSQSim events, once DB is populated | ||
*Produce candidate site list for Bay Area CyberShake | *Produce candidate site list for Bay Area CyberShake | ||
| − | * | + | *Investigate improved load-balancing for DirectSynth SGT handlers |
| + | *Experiment with OMP parallelization for post-processing | ||
Latest revision as of 17:56, 1 February 2018
Current Items
- Modify CyberShake to work on RSQSim ruptures
- Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
- CyberShake training
- Update CyberShake study wiki pages to point to SQLite files
- Create wiki page for CyberShake RSQSim, and upload sample seismograms
Project Backlog
- Run CyberShake post-processing on RSQSim events, once DB is populated
- Produce candidate site list for Bay Area CyberShake
- Investigate improved load-balancing for DirectSynth SGT handlers
- Experiment with OMP parallelization for post-processing
