Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(23 intermediate revisions by the same user not shown)
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 ==
*Regenerate Study 15.4 SGTs for the 23 broadband station sites requested by Hong Kie.
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
 
+
*Produce candidate site list for Bay Area CyberShake
*Generate grid for John and Andreas.  Figure out how to go from set of volumes into one super-volume.
+
*Investigate improved load-balancing for DirectSynth SGT handlers
 
+
*Experiment with OMP parallelization for post-processing
*Generate Z1.0, Z2.5 plots for Kevin.  Couldn't find output files, so resubmitted with full paths.
 
 
 
*Email B-maps to Morgan
 
 
 
*Email Gideon about paper
 
 
 
*Reproduce Feng's results using ABF
 
 
 
*Run tests with SBSM, USC, PAS with v5.2.3.  Checked on BBP and found v5.2.2; try to determine difference.
 
 
 
*Finish technical stats for Study 17.3
 
 
 
*Work on CyberShake training guide
 
 
 
*Work on RSQSim workflow tool
 
 
 
*Respond to students @ SC
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
== Areas of Responsibilities ==
 
* CyberShake
 
* Broadband CyberShake
 
* Code migration
 

Latest revision as of 17:56, 1 February 2018

Current Items

  • 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

Project Backlog

  • Run CyberShake post-processing on RSQSim events, once DB is populated
  • Produce candidate site list for Bay Area CyberShake
  • Investigate improved load-balancing for DirectSynth SGT handlers
  • Experiment with OMP parallelization for post-processing