Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(592 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Monitor Stampede scratch deletes
+
*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
  
=== BW Workflow ===
+
== Project Backlog ==
*Continued workflow testing on BW - finished SGT workflow, starting PP
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
 
+
*Produce candidate site list for Bay Area CyberShake
=== 1 Hz ===
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Check results of AWP format velocity test - passed (diff < 1.7e-05 %)
+
*Experiment with OMP parallelization for post-processing
*Continued monitoring RV inserts
 
*Ran RWG merge job
 
*Tried to determine points for SGT comparison - stupid way takes too long
 
 
 
== Today ==
 
*Run pegasus-statistics when Python is upgraded on aftershock
 
 
 
=== BW Workflow ===
 
*Ask John to upgrade RLS
 
*BW down today
 
 
 
=== 1 Hz ===
 
*Use smarter way to get points for SGT comparison
 
*Compare 1 Hz and 0.5 Hz RWG SGTs
 
*Pause RV inserts - adjust to do just RV inserts, then come back and do hypos
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*Security meeting with Phil?
 
 
 
== 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