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
 
(804 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Convert velocity models to AWP format for hazard curve on HPC, sent back to Kraken
*Modify CyberShake to work on RSQSim ruptures
*Issue with RWG SGT v3.0.3 - looks like I forgot to copy over loop change
**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


== Today ==
== Project Backlog ==
*Email CyberShake papers to Liwen
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Submit hazard curve jobs with AWP SGTs
*Produce candidate site list for Bay Area CyberShake
*Copy loop change, try RWG SGT v3.0.3 again
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Experiment with OMP parallelization for post-processing
== Blocked ==
*No
 
== Follow-ups ==
*No
 
 
 
*Continue testing compiler optimizations
*Run some I/O tests to get reference values
 
 
== 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