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 ==
-*Retried integrated DAX generator SGT jobs - finished SGT workflow, but had staging/registration problem
+*Modify CyberShake to work on RSQSim ruptures
-*Tried to get statistics from PP runs, but pegasus-stats/monitord issue
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Submitted more runs with Kim's new code
+*CyberShake training
-*Submitted another run with Rob's v1.16.3
+*Update CyberShake study wiki pages to point to SQLite files
-*Successfully logged into Blue Waters portal
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*CyberShake calls
-== Today ==
+== Project Backlog ==
-*Modify integrated DAX gen to stage/register SGTs
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Monitor Rob's v1.16.3 run, produce reciprocity seismograms when done
+*Produce candidate site list for Bay Area CyberShake
-*Fix pegasus-stats issue
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Create directory hierarchy for seismogram, PSA files
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*No
-== Follow-ups ==
-*Interview with David
-*Runs for Rob and Kim
-*Continue testing compiler optimizations
-*Run some I/O tests to get reference values
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration