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
 
(655 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 on coscheduling
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Stampede
*CyberShake training
**Post-processed SGT GPU results, at least some seismograms are wrong
*Update CyberShake study wiki pages to point to SQLite files
*Call with Omar with heads-up for Study 13.4
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Blue Waters
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Continue work on coscheduling
*Produce candidate site list for Bay Area CyberShake
**Start analyzing SGT GPU results to determine source of error
*Investigate improved load-balancing for DirectSynth SGT handlers
*Generate new data products for Rob to understand velocity differences
*Experiment with OMP parallelization for post-processing
*Identify directories used in 2011-12 CyberShake runs and zip
*Email Rob, ask about high SBSM ground motions
*If John upgraded aftershock disk, rerun monitord population
 
== Blocked ==
*No
 
== Follow-ups ==
*GB call?
*Blue Waters user call at 1
 
Check on SA forward sim
Email Stampede staff, let them know about node crashing solution
Finish wiki entries for Stampede and Blue Waters validation
 
== 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"