Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(870 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Finished slides for Rob/Kim/Tom/Phil discussion Monday
+
*Modify CyberShake to work on RSQSim ruptures
*Prepared full-scale CyberShake SGT run to get AWP runtime for slides
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Investigated why close SGTs result in bigger seismogram difference, no solution yet
+
*CyberShake training
*Ran new pegasus-mpi-cluster, ran to disagg step
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Send draft slides to Phil
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Calculate SGT stats for no-averaging run
+
*Produce candidate site list for Bay Area CyberShake
*Submit SGTs with lower velocities, SGTs with Q
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Read over Pegasus abstract
+
*Experiment with OMP parallelization for post-processing
*Try hazard curve with JBSim3d_PSA
 
*Submit double-couple run
 
*Register rupture geometry files on Kraken in RLS
 
*Submit full-scale CyberShake SGT run
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
 
 
*Compare En-Jui's SGT results to AWP
 
 
 
 
 
== Areas of Responsibilities ==
 
* CyberShake 1.4
 
* Broadband CyberShake
 
* Code migration
 
 
 
*Create bio, work summary, abstract for EU-US summer school
 

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