Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older edit
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
 
(293 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Finished RotD insertion
*Modify CyberShake to work on RSQSim ruptures
*Email seismograms to Glenn
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Tested BBP install on Stampede, queued job to do tests
*CyberShake training
*Generated plots for wiki for science review
*Update CyberShake study wiki pages to point to SQLite files
*Updated DAX generator to support separate source filtering frequency
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Added column to DB to track source filtering frequency
*Started refactoring argument management for create/plan/run scripts
*Modified the header generation code to take filtering frequency, not simulation frequency, for determining the time delay


== Today ==
== Project Backlog ==
*Assemble slides for science review, email to Phil for review
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Finish RotD curve calc, let Kevin know
*Produce candidate site list for Bay Area CyberShake
*Check on BBP test results on Stampede
*Investigate improved load-balancing for DirectSynth SGT handlers
*Continue refactoring argument handling in create/plan/run scripts
*Experiment with OMP parallelization for post-processing
*Modify Titan pilot daemon to query for new Pegasus parameter
*Modify auto-submit to handle SGT vs PP workflows
*Modify auto-submit to handle dynamic assignment of workflows to resources
*Run simultaneous tests of Blue Waters and Titan workflows
 
== Blocked ==
*No
 
== Follow-ups ==
*HighF call
 
== 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
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Scott&oldid=19663"