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
 
(690 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Continued working through workflow creator - integrating with RunManager
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Kraken:
*CyberShake training
**Moved seismogram extraction to shock
*Update CyberShake study wiki pages to point to SQLite files
*Extracted forward seismograms - after a few false starts, sent results to Rob for review
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Added support for multiple runs with same site in RunManager
*Started wiki entries for Blue Waters and Stampede validation
*Think about readiness review
*Think about access to CyberShake data


 
== Project Backlog ==
== Today ==
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Blue Waters:
*Produce candidate site list for Bay Area CyberShake
**Add support for data movement when SGT jobs complete
*Investigate improved load-balancing for DirectSynth SGT handlers
**Test RunManager integration and qsub dependencies
*Experiment with OMP parallelization for post-processing
*Stampede:
**Follow-up with GRAM group re: hanging Perl script
*Kraken:
**Post-process 4 sets of WNGC SGTs and test support for multiple runs with same site
*Email ISI to ask about gathering metrics from Study 2.2
*Complete wiki entries for Blue Waters and Stampede validation
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
== Areas of Responsibilities ==
* CyberShake 1.4
* 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"