Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(952 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Yesterday ==
+
== Current Items ==
−
*Continuing to investigate the 3D issue - Rob suspects a AWP problem
+
*Modify CyberShake to work on RSQSim ruptures
−
*Tested out pegasus 4.0.0, successful executions
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
−
*Data management meeting
+
*CyberShake training
−
*Resumed automatic CyberShake runs
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
−
== Today ==
+
== Project Backlog ==
−
*Extract 1D profiles of velocity models for Rob
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
−
*Continue work on MPI I/O for SGT Merge
+
*Produce candidate site list for Bay Area CyberShake
−
*Add memcached to in-memory RV generation
+
*Investigate improved load-balancing for DirectSynth SGT handlers
−
*Try 27x weak scaling test on Kraken
+
*Experiment with OMP parallelization for post-processing
−
 
 
−
== Blocked ==
 
−
*No
 
−
 
 
−
== Follow-ups ==
 
−
*None
 
−
 
 
−
== 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