Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older edit
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
 
(664 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Continued USC workflows, submitted SBSM, a few wallclock time exceeds
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Stampede:
*CyberShake training
**Continued post-processing runs
*Update CyberShake study wiki pages to point to SQLite files
*Kraken:
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Emailed NICS staff to check in
**Started forward San Andreas simulation
*Started plotting comparison curve for wiki: SBSM CVM-H curves look like CVM-S


== Today ==
== Project Backlog ==
*Blue Waters:
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Finish remaining USC workflow
*Produce candidate site list for Bay Area CyberShake
**Finish remaining SBSM workflow
*Investigate improved load-balancing for DirectSynth SGT handlers
**Add restart capability to workflows
*Experiment with OMP parallelization for post-processing
**Determine why CVM-H and CVM-S wfs look very similar for SBSM
*Stampede:
**Post-process USC, SBSM workflows when complete
*Kraken
**Check on San Andreas forward simulation
*Start monitord run on aftershock
*Ask David for help with velocity comparison plots
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
Finish wiki entries for Stampede and Blue Waters validation
Think about readiness review
Think about access to CyberShake data
 
== Areas of Responsibilities ==
* CyberShake 1.4
* Broadband CyberShake
* Code migration

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
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Scott&oldid=19663"