Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(904 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Yesterday ==
+
== Current Items ==
−
*Continued testing new version of JBSim3d
+
*Modify CyberShake to work on RSQSim ruptures
−
*Checked on AWP forward run, got OOM errors - asked Yifeng for help
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
−
*Checked on s351 workflow run, calculated some PP metrics - error, waiting on fix for better ones
+
*CyberShake training
 +
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
−
== Today ==
+
== Project Backlog ==
−
*Try PP workflow with new JBSim3d
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
−
*Edit workflow paper (Word version)
+
*Produce candidate site list for Bay Area CyberShake
−
*Read AWP document from Yifeng about source, make adjustments
+
*Investigate improved load-balancing for DirectSynth SGT handlers
−
*Queue up new suggested runs from Kim and Rob
+
*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