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 ==
-*Generated list of metrics to produce from Kraken runs, emailed to Phil
+*Modify CyberShake to work on RSQSim ruptures
-*Tested JBSim3d with header files - good curves
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*RWG and AWP halfspace runs completed
+*CyberShake training
-*Use reciprocity to generate Z seismograms with RWG and AWP - not very similar, SGTs didn't look good either
+*Update CyberShake study wiki pages to point to SQLite files
-*Submitted rot Z run, since that looked good in the past
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Extracted seismograms at TEST site location from RWG and AWP forward runs - not very similar
-== Today ==
+== Project Backlog ==
-*Add CVM-H basin depth in ARs ticket to CyberShake trac
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Check on rot Z run
+*Produce candidate site list for Bay Area CyberShake
-*Check source description in forward run
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Add merged PSA calculation option to JBSim3d
+*Experiment with OMP parallelization for post-processing
-*Synthesize seismograms from halfspace runs
-== Blocked ==
-*No
-== Follow-ups ==
-*With Phil re: storage
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration