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
 
(694 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Resolve velocity model issues, passed validation
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Stampede:
*CyberShake training
**Investigated issues behind stage-out of job status:  looks like scontrol stops being called
*Update CyberShake study wiki pages to point to SQLite files
**Tried test with slurm2, same problem
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Found typo in logging
*Kraken:
**Queued up forward simulation
*Started putting Blue Waters information on internal wiki


== Today ==
== Project Backlog ==
*Blue Waters:
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Continue working through workflow creator
*Produce candidate site list for Bay Area CyberShake
*Stampede:
*Investigate improved load-balancing for DirectSynth SGT handlers
**Continue investigating GRAM issues
*Experiment with OMP parallelization for post-processing
*Kraken:
**Monitor forward simulation
*Finish putting Blue Waters information on internal wiki
*Wiki entries for Blue Waters and Stampede validation
 
== Blocked ==
*No
 
== Follow-ups ==
*CyberShake calls
 
== 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