Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older edit
Scottcal (talk | contribs)
8,097 edits
mNo edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
 
(774 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Monitored production runs - very few cores available, no jobs run in past 12 hours
*Modify CyberShake to work on RSQSim ruptures
*Major hit to SUs on Kraken - down 1.4M from last update (weekly?) - tera3d used 20k since last update
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Finished SC12 abstract with Kevin and Phil's help
*CyberShake training
*Finished implementing seismogram and PSA headers, small tests pass
*Update CyberShake study wiki pages to point to SQLite files
*Started work on changes to PSA insertion to use headers
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Worked on public wiki page with Study 2.2
*Got request for peak values from Maren
*Yifeng has questions regarding his XSEDE presentation


== Today ==
== Project Backlog ==
*Monitor production runs
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Finish changes to PSA insertion
*Produce candidate site list for Bay Area CyberShake
*Run test with file headers
*Investigate improved load-balancing for DirectSynth SGT handlers
*Finish study wiki page, send to Phil
*Experiment with OMP parallelization for post-processing
*Respond to Maren
*Respond to Yifeng
*Add description of seismogram and PSA header design decisions
 
== Blocked ==
*No
 
== Follow-ups ==
*CyberShake calls
 
 
*Run test of I/O forwarding on Kraken
*Continue testing compiler optimizations
*Run some I/O tests to get reference values
 
 
== 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"