Difference between revisions of "Staff Priorities - Scott"

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 ==
-*Ran PP with AWP SGTs - a few workflows terminated, rerunning
+*Modify CyberShake to work on RSQSim ruptures
-*RWG TEST SGT runs competed on HPC, submitted PP
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*RWG USC SGT runs completed
+*CyberShake training
-*Meeting with Phil
+*Update CyberShake study wiki pages to point to SQLite files
-*CyberShake call
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Initial test of UCVM in AWP format does not agree with reference
-*Gideon finished piping code "I/O forwarding"
-*Started getting list of sites together for production run
-== Today ==
+== Project Backlog ==
-*Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Check UCVM AWP results - start with projection
+*Produce candidate site list for Bay Area CyberShake
-*Run test of I/O forwarding on Kraken
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Track down SGTs for production run
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-*Email CyberShake papers to Liwen
-*Continue testing compiler optimizations
-*Run some I/O tests to get reference values
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration