Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(74 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 ==
*Check on USC Study 15.4 verification run on Titan
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Check on s001 run on Titan
+
*Produce candidate site list for Bay Area CyberShake
*Change legend on seismogram plots
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Pull northern seismogram to make sure NT is large enough
+
*Experiment with OMP parallelization for post-processing
*Put new study ID in db
 
 
 
*Make spreadsheet comparing models, with identifiers, inputs, and relevant motivations
 
*Make spreadsheet with computational stats, metrics to compare size and performance
 
*Create GP07/GP10/GP14 comparison plots
 
*Create hazard maps with same basemap and same color scale
 
*Start on computational section
 
 
 
*Check on CyberShake on Cori after Wed
 
*Propose experiments on Google doc
 
 
 
*Get blurb added to website with timeframe for mentoring call
 
*Pull out into doc the questions we asked on last year's application, email to group
 
 
 
== 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