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 ==
-*Respond to Mats's questionnaire about data integrity for Pegasus
+*Modify CyberShake to work on RSQSim ruptures
-*Review 2017 IHPCSS proposal
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Produce writeup on 2017 IHPCSS mentoring activities
+*CyberShake training
-*Create and email link to images of Vp, Vs, Rho without cutoffs
+*Update CyberShake study wiki pages to point to SQLite files
-*Register and use ALCF token
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Run USC site on Blue Waters and Titan with Study 15.4 parameters, compare hazard curves and a few time series
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Verify smoothing in workflow produces correct results
+*Produce candidate site list for Bay Area CyberShake
-*Something funky with cleanup jobs - shouldn't be running as gridftp jobs.  Turned off cleanup on Titan for now.
+*Investigate improved load-balancing for DirectSynth SGT handlers
+*Experiment with OMP parallelization for post-processing
-*Check cleanup test
-*Run same site on Titan as BW
-*Consider running all PP on BW
-*Compare seismograms with BW vs Study 15.4 test
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake
-* Broadband CyberShake
-* Code migration