Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
 
*Blue Waters
 
*Blue Waters
**Continued working on coscheduling
+
**Worked on debugging GPU code
*Stampede
+
*Emailed Rob about SBSM high ground motions
**Post-processed SGT GPU results, at least some seismograms are wrong
+
*Emailed Rob with new velocity plots
*Call with Omar with heads-up for Study 13.4
 
  
 
== Today ==
 
== Today ==
 
*Blue Waters
 
*Blue Waters
 +
**Reformat GPU SGTs for calculating hazard curve
 
**Continue work on coscheduling
 
**Continue work on coscheduling
**Start analyzing SGT GPU results to determine source of error
 
*Generate new data products for Rob to understand velocity differences
 
 
*Identify directories used in 2011-12 CyberShake runs and zip
 
*Identify directories used in 2011-12 CyberShake runs and zip
*Email Rob, ask about high SBSM ground motions
 
 
*If John upgraded aftershock disk, rerun monitord population
 
*If John upgraded aftershock disk, rerun monitord population
  
Line 20: Line 17:
 
== Follow-ups ==  
 
== Follow-ups ==  
 
*GB call?
 
*GB call?
*Blue Waters user call at 1
 
  
 
Check on SA forward sim
 
Check on SA forward sim

Revision as of 17:33, 16 April 2013

Yesterday

  • Blue Waters
    • Worked on debugging GPU code
  • Emailed Rob about SBSM high ground motions
  • Emailed Rob with new velocity plots

Today

  • Blue Waters
    • Reformat GPU SGTs for calculating hazard curve
    • Continue work on coscheduling
  • Identify directories used in 2011-12 CyberShake runs and zip
  • If John upgraded aftershock disk, rerun monitord population

Blocked

  • No

Follow-ups

  • GB call?

Check on SA forward sim Email Stampede staff, let them know about node crashing solution Finish wiki entries for Stampede and Blue Waters validation

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration