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
 
(361 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Modified Titan pilots to abort if not enough walltime remaining
*Modify CyberShake to work on RSQSim ruptures
*Modified Titan workflow jobs to only match if enough walltime left
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Full-scale 0.5Hz workflow with RotD test on Blue Waters verified (few small issues with workflow)
*CyberShake training
*Bug in random vs uniform hypocenter test, fixed, resubmitted
*Update CyberShake study wiki pages to point to SQLite files
*Monitor Titan 1 Hz SGTs for PAS, SBSM
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Generated results from 100m mesh at 0.5 Hz, seismograms suggest a scaling issue
*Found hard-coded values in SGT header generation, emailed Rob


== Today ==
== Project Backlog ==
*Generate estimate of single pilot job size for Titan workflow
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Monitor uniform vs random hypocenter test
*Produce candidate site list for Bay Area CyberShake
*Start on presentation for HPCC booth
*Investigate improved load-balancing for DirectSynth SGT handlers
*Set up meeting time at SC14 with NCSA staff
*Experiment with OMP parallelization for post-processing
*Email Matt Norman to see if he'll be at SC14
*Set up meeting at SC14 with ISI group
*Get feedback from Rob and Kim about SGT header hard-coded values
 
== Blocked ==
*No
 
== Follow-ups ==
*HighF
*CyberShake
*Shakeout Discussion
 
== 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"