Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(955 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Compared SGTs from workflow SMALL site to by-hand SMALL site - looks fine
+
*Modify CyberShake to work on RSQSim ruptures
*Submitted run testing theory about rotation
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Tried Pegasus 4.0.0 with TEST curve, ran into issue, emailed Karan
+
*CyberShake training
*Ran TEST curve with in-mem RV generation on Ranger, passed
+
*Update CyberShake study wiki pages to point to SQLite files
*Discovered slow performance of SGTMerge step with full-scale SGTs on Kraken
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Checked results from profiling test on Kraken - some kind of corruption in TAU files, emailed Matt
 
  
== Today ==
+
== Project Backlog ==
*Adjusted SGT Merge parameters on Kraken, trying again - may need MPI I/O
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Email Rob F2F ruptures, ask for thoughts
+
*Produce candidate site list for Bay Area CyberShake
*CyberShake call
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Check newest run results with 3D issue
+
*Experiment with OMP parallelization for post-processing
*Finish interrupted PP runs on Ranger
 
*Add memcached to in-memory RV generation
 
*Try 27x weak scaling test on Kraken
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*CyberShake call
 
 
 
== 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