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
 
(930 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Responded to Jessica's questions
*Modify CyberShake to work on RSQSim ruptures
*Did comparison between my and Shiyu's results - small differences, but Kraken upgrade since
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Tried running AWP-ODC myself
*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 ==
*Do 1D runs using profile below site location
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Try same 1D run as Shiyu to compare
*Produce candidate site list for Bay Area CyberShake
*Prepare run for TEST site for hazard curve generation
*Investigate improved load-balancing for DirectSynth SGT handlers
*Mail off notary form
*Experiment with OMP parallelization for post-processing
*Look over agendas for next week's meetings
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
== 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