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
 
(82 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== 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 ==
== Today ==
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Use new 1D model created by David with projection fix
*Produce candidate site list for Bay Area CyberShake
*Run USC site on Blue Waters and Titan with Study 15.4 parameters, compare hazard curves and a few time series
*Investigate improved load-balancing for DirectSynth SGT handlers
*Register and use ALCF token
*Experiment with OMP parallelization for post-processing
*Add smoothing steps to workflow, verify with reference
*Something funky with cleanup jobs - shouldn't be running as gridftp jobs.  Turned off cleanup on Titan for now.
 
== 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