Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Emailed Tom comparison curves - Tom requested revisions
+
*Summer School call
*genslip-v3.3.1b results match expected
+
*CyberShake technical call
*Ran profiling on rupture generation code - found bubble sort, sped up code 93%
+
*Upgraded Globus to 5.2.5, fixed issues
 +
*Emailed Rob to ask about varying numbers of hypocenters
  
 
== Today ==
 
== Today ==
*Integrate Phil's edits to Extreme Scaling abstract, email out to broader group
+
*Point Efecan to coscheduling examples on Blue Waters
*Kevin and I will revise curves for Tom tomorrow
+
*Integrate changes to Extreme Scaling abstract
*Monitor USC 36 run
+
*Once get OK from Rob, create new RV ID for uniform hypos
*Remove sort, retest
+
*Run verification test of TEST site with random hypos on Blue Waters
*Run TEST site with uniform hypos
 
 
*Get timing data with rupture variation generator to Yifeng
 
*Get timing data with rupture variation generator to Yifeng
 
*Run test to see if locality matters
 
*Run test to see if locality matters
Line 17: Line 17:
  
 
== Follow-ups ==
 
== Follow-ups ==
*No
+
*Phil to discuss NCSA questions
  
  

Revision as of 17:02, 30 April 2014

Yesterday

  • Summer School call
  • CyberShake technical call
  • Upgraded Globus to 5.2.5, fixed issues
  • Emailed Rob to ask about varying numbers of hypocenters

Today

  • Point Efecan to coscheduling examples on Blue Waters
  • Integrate changes to Extreme Scaling abstract
  • Once get OK from Rob, create new RV ID for uniform hypos
  • Run verification test of TEST site with random hypos on Blue Waters
  • Get timing data with rupture variation generator to Yifeng
  • Run test to see if locality matters

Blocked

  • No

Follow-ups

  • Phil to discuss NCSA questions


  • Try out SeedMe so I can respond to Amit


Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration