Staff Priorities - Scott: Difference between revisions

Latest revision as of 17:56, 1 February 2018

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

@@ Line 1: / Line 1: @@
-== Yesterday ==
+== Current Items ==
-*SRF staging completed, resubmitted workflow on Kraken
+*Modify CyberShake to work on RSQSim ruptures
-*Ran seismograms by hand with AWP and RWG, investigated big differences - was using wrong SGT X file
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Continued development of JBSim3d + memcached + in-mem RV + PSA calculation
+*CyberShake training
-*Did performance review preparation
+*Update CyberShake study wiki pages to point to SQLite files
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Consider different filtering with RWG code - explain difference in PSA values?
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Continued development of JBSim3d + memcached + in-mem RV + PSA calculation (need to refactor)
+*Produce candidate site list for Bay Area CyberShake
-*Monitor LGU PP workflow on Kraken
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Do fwd run of extended source with AWP and RWG to compare
+*Experiment with OMP parallelization for post-processing
-*Email Kim raw data for extended source
-*Look up better # of CS runs for 2012
-== Blocked ==
-*No
-== Follow-ups ==
-*CyberShake call
-*Performance review with Phil
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration