Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(929 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Tried same 1D profile run as Shiyu to compare - difference, asked Shiyu for IN3D files
+
*Modify CyberShake to work on RSQSim ruptures
*Prepared for TEST site for hazard curve generation, asked Shiyu to run
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Look over agendas for next week's meetings
+
*CyberShake training
*Error with RWG 1D profile run, resubmitted
+
*Update CyberShake study wiki pages to point to SQLite files
*Got pointed to AWP mesh generation code from Patrick
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Add new SGT Variation to DB for AWP-ODC-SGT
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Compare profile run results
+
*Produce candidate site list for Bay Area CyberShake
*Try creating AWP-ODC-SGT post-processing workflow
+
*Investigate improved load-balancing for DirectSynth SGT handlers
 
+
*Experiment with OMP parallelization for post-processing
== 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