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 ==
-*Po responded explaining averaging
+*Modify CyberShake to work on RSQSim ruptures
-*Issues with elastic AWP run, stalled, Kim suggests abandoning
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Determined memory requirements, added hints to SGT generator
+*CyberShake training
-*Compiled new pegasus-mpi-cluster, new planner
+*Update CyberShake study wiki pages to point to SQLite files
-*En-Jui pointed me to SGT results
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Compare En-Jui's SGT results to AWP
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Continue investigating code to translate stresses to SGTs
+*Produce candidate site list for Bay Area CyberShake
-*Try AWP run with xyn, xzn, yzn averaging commented out
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Try hazard curve with JBSim3d_PSA
+*Experiment with OMP parallelization for post-processing
-*Test out new pegasus-mpi-cluster
-*Try fwd runs with double-couple source
-*Try velocity comparison for simple run
-== Blocked ==
-*No
-== Follow-ups ==
-*Meeting with Phil at 11
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration
-*Create bio, work summary, abstract for EU-US summer school