Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(335 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*HighF call
+
*Modify CyberShake to work on RSQSim ruptures
*Emailed Glenn sample queries
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Transfer issues is related to hpc-transfer certificates
+
*CyberShake training
*Resumed PAS 1 Hz transfers, found and fixed issue with RotD file
+
*Update CyberShake study wiki pages to point to SQLite files
*Monitor Titan SGTs, SBSM complete
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Continued debugging DirectSynth (~30%)
 
  
== Today ==
+
== Project Backlog ==
*With Kevin's help, finish PAS 1 Hz workflow
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Transfer SBSM SGTs
+
*Produce candidate site list for Bay Area CyberShake
*Begin 1 Hz SBSM run on Blue Waters
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Continue debugging DirectSynth
+
*Experiment with OMP parallelization for post-processing
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*CyberShake calls
 
 
 
== Areas of Responsibilities ==
 
* CyberShake
 
* 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