Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Scottcal (talk | contribs)
No edit summary
Scottcal (talk | contribs)
No edit summary
 
(718 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Started testing AWP-ODC-SGT helper scripts
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Validated RWG TEST V3 SGTs
*CyberShake training
*Stampede:
*Update CyberShake study wiki pages to point to SQLite files
**Ran GRAM tests, reported issues
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Started configuring SGT workflow
*Kraken:
**Finished running available post-processing runs
*Construct computational and data estimates for AWP and RWG SGTs on Blue Waters for CVM-S and CVM-H maps


== Today ==
== Project Backlog ==
*Blue Waters:
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Finish testing AWP-ODC-SGT helper scripts, validate results
*Produce candidate site list for Bay Area CyberShake
**Run and validate RWG TEST V3.0.3 SGTs
*Investigate improved load-balancing for DirectSynth SGT handlers
*Stampede:
*Experiment with OMP parallelization for post-processing
**Finish configuring SGT workflow, validate results
**Configure PP workflow, validate results
*Kraken:
**Use to validate SGTs from Blue Waters and Stampede
**Select a rupture for forward simulation
**Run some V3.0.3 SGTs for next map
*Prepare for performance review tomorrow
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
 
*Watch Morgan's AGU presentation
*Reply to TACC, NICS regarding authorized people
 
== 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