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
 
(662 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters
*Modify CyberShake to work on RSQSim ruptures
**Designed and built system for auto-submission (like on shock)
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Worked on debugging AWP-ODC-SGT GPU code - may have found bug
*CyberShake training
*Stampede
*Update CyberShake study wiki pages to point to SQLite files
**Started working with offloading with RWG V3.0.3 -- need to make code changes
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Improved RWG V3.0.3 vectorization, 11% improvement
*Kraken
**Error with San Andreas forward simulation, resubmitted


== Today ==
== Project Backlog ==
*Blue Waters
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Test auto-submit system
*Produce candidate site list for Bay Area CyberShake
**Continue working on AWP-ODC-SGT GPU code
*Investigate improved load-balancing for DirectSynth SGT handlers
**Profile vectorized RWG code
*Experiment with OMP parallelization for post-processing
*Stampede
**Continue working on offloading
*Kraken
**Check on SA forward sim
*Email Stampede staff, let them know about node crashing solution
 
== Blocked ==
*Waiting on John to create DB to move ahead with monitord population
 
== 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"