Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(30 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.  Same configuration as Study 15.4, but no GTL.  Either use 'cvms5' with GTL turned off in config file, or use 'cvmsi' and ignore the GTL issue.
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
 
+
*Produce candidate site list for Bay Area CyberShake
*Generate grid for John Shaw.  Talked with Phil - present options to John of either 100m (so cal) or 175m (cen cal). 500m harder to work with.  Email John and give options.
+
*Investigate improved load-balancing for DirectSynth SGT handlers
 
+
*Experiment with OMP parallelization for post-processing
*Generate Z1.0, Z2.5 plots for Kevin.  Try reinstalling UCVM on BW so we can do this in parallel.
 
 
 
*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
 
 
 
*Check on Darshan profiling of Cori code
 
 
 
*Work on RSQSim workflow tool
 
 
 
*Work on CyberShake training guide
 
 
 
*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