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
 
(594 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Submitted comments on Maren's CyberShake paper
*Modify CyberShake to work on RSQSim ruptures
*Resubmitted Stampede scratch deletes
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*su to tera3d working on Stampede, asked Yaakoub for aid with getting proxy
*CyberShake training
*Update CyberShake study wiki pages to point to SQLite files
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


=== BW Workflow ===
== Project Backlog ==
*Still issues with two-factor certificate and RLS; Gideon recommended RLS upgrade when John returns
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Continued workflow testing on BW - issue with h2ologin4, Tim installed GRAM on h2ologin1-3
*Produce candidate site list for Bay Area CyberShake
 
*Investigate improved load-balancing for DirectSynth SGT handlers
=== 1 Hz ===
*Experiment with OMP parallelization for post-processing
*Continued monitoring RV inserts
*Ran RWG SGT generator at 1 Hz
*Asked CyberShake group about velocity cutoffs - sounds like we should keep the same ones
 
 
== Today ==
*Run pegasus-statistics when Python is upgraded on aftershock
*Monitor Stampede scratch deletes
 
=== BW Workflow ===
*Continue workflow testing on BW
 
=== 1 Hz ===
*Check results of AWP format velocity test
*Continue monitoring RV inserts
*Run RWG merge job, compare 1 Hz and 0.5 Hz SGTs
 
== 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"