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
 
(119 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Meeting with Phil and Kevin re: adding RSQSim to SCEC SVN
*Modify CyberShake to work on RSQSim ruptures
*Intern prep call
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Created proposed CCSP box
*CyberShake training
*Fixed number of digits alloted to dimensions in SGT header, resubmitted
*Update CyberShake study wiki pages to point to SQLite files
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Resubmit seismogram synthesis, see if seg fault disappears
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Create new CCSP box
*Produce candidate site list for Bay Area CyberShake
*Add So Cal box to plot
*Investigate improved load-balancing for DirectSynth SGT handlers
*Edit IHPCSS mentoring docs
*Experiment with OMP parallelization for post-processing
*Update Study 15.12 wiki
*Start working on intern HPC presentation
*Customize SCEC-VDO navigation
*Update DB migration plan
*Match mentors and mentees for IHPCSS
*Update wiki with CyberShake specification template
*Update wiki with process for defining CyberShake box
*Create dummy sites at box corners; determine volume size
*Get CyberShake estimates for allocation proposal: CCSP for 900 m/s and 500 m/s, 1 Hz; also So Cal with UCERF 3 tests
 
== Blocked ==
*No
 
== Follow-ups ==
*CyberShake call at 11
 
== 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