Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(959 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Narrowed down RWG 3D issue to input files; ran SMALL site to help with debugging
+
*Modify CyberShake to work on RSQSim ruptures
*Got in trouble on Ranger
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Got rupture geometries from Kevin for F2F ruptures
+
*CyberShake training
*Checked
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Try Pegasus 4.0.0 with TEST curve
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Run TEST curve with in-mem RV generation on Ranger
+
*Produce candidate site list for Bay Area CyberShake
*Run post-processing for full CS site with Kraken SGTs
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Email Rob F2F ruptures, ask for thoughts
+
*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