Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(471 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Summer School call
+
*Modify CyberShake to work on RSQSim ruptures
*CyberShake calls
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*May 12 call
+
*CyberShake training
*Started inserting 2s PSA values into DB from Study 14.2 as requested by Tom
+
*Update CyberShake study wiki pages to point to SQLite files
*Plotted comparison curves of 200m v 1000m TEST site, presented at call
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Email 200m v 1000m curves to the group
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Email Tom when insertion of 2s is complete
+
*Produce candidate site list for Bay Area CyberShake
*Email Rob, suggesting we try uniformly distributed hypocenters in rupture variation
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Generate comparison curves for May 12 sites from Study 14.2, all 3 velocity models, 3 and 5 sec
+
*Experiment with OMP parallelization for post-processing
*Check FFTW version of rupture generator for similarity of results
 
*Get timing data with rupture variation generator to Yifeng
 
*Run test to see if locality matters
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*BBP code review at 1:30
 
 
 
 
 
*Try out SeedMe so I can respond to Amit
 
 
 
 
 
 
 
== 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