Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Tried out Lync with Blue Jeans - success!
+
*Summer School call
*Debugged new seg faults, produced 200m curve, looks good
+
*CyberShake calls
*Tested FFTW version of rupture generator - 5% faster
+
*May 12 call
 +
*Started inserting 2s PSA values into DB from Study 14.2 as requested by Tom
 +
*Plotted comparison curves of 200m v 1000m TEST site, presented at call
  
 
== Today ==
 
== Today ==
*Insert 2s PSA values into DB from Study 14.2, all 3 velocity models
+
*Email 200m v 1000m curves to the group
*Plot comparison curves of 200m v 1000m TEST site
+
*Email Tom when insertion of 2s is complete
 +
*Generate comparison curves for May 12 sites from Study 14.2, all 3 velocity models, 3 and 5 sec
 
*Check FFTW version of rupture generator for similarity of results
 
*Check FFTW version of rupture generator for similarity of results
 
*Get timing data with rupture variation generator to Yifeng
 
*Get timing data with rupture variation generator to Yifeng
Line 15: Line 18:
  
 
== Follow-ups ==
 
== Follow-ups ==
*CyberShake calls
+
*BBP code review at 1:30
*May 12 planning call (2 pm)
 
  
  

Revision as of 17:18, 23 April 2014

Yesterday

  • Summer School call
  • CyberShake calls
  • May 12 call
  • Started inserting 2s PSA values into DB from Study 14.2 as requested by Tom
  • Plotted comparison curves of 200m v 1000m TEST site, presented at call

Today

  • Email 200m v 1000m curves to the group
  • Email Tom when insertion of 2s is complete
  • Generate comparison curves for May 12 sites from Study 14.2, all 3 velocity models, 3 and 5 sec
  • 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