Staff Priorities - Scott: Difference between revisions

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 tests with SBSM, USC, PAS with v5.2.3.  Check with Fabio that 5.2.3 is the current version on the BBP.
+*Run CyberShake post-processing on RSQSim events, once DB is populated
+*Produce candidate site list for Bay Area CyberShake
-*Reproduce Feng's results using ABF
+*Investigate improved load-balancing for DirectSynth SGT handlers
+*Experiment with OMP parallelization for post-processing
-*Finish technical stats for Study 17.3
-*Monitor CyberShake workflow on Cori
-*Work on RSQSim workflow tool
-*Work on CyberShake training guide
-*Draft student outreach idea at SC17: focus group with students, how can we improve their experience?
-*Think about people I know who might be able to give a webinar
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake
-* Broadband CyberShake
-* Code migration