Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Scottcal (talk | contribs)
No edit summary
Scottcal (talk | contribs)
No edit summary
 
(66 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 ==
*Tag code in repository
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Start cron job to monitor certs
*Produce candidate site list for Bay Area CyberShake
 
*Investigate improved load-balancing for DirectSynth SGT handlers
*Review and edits slides for workflow talk
*Experiment with OMP parallelization for post-processing
 
*Upload Feng's images to wiki page
*Start on computational section
 
*Submit CyberShake workflow on Cori
 
*Email out samples of text to mentoring committee
 
*Look at ways to connect with SC student tracks
*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

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