Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*BBP release call
+
*BBP BBToolbox unit test failed on Blue Waters, will retry RC2
*Call with Phil
+
*BBP acceptance tests passed
*Tried running BBP unit tests on Blue Waters: took longer than 4 hours, resubmitted with 48
+
*Workflow virtual summer school planning call, being asked to give intro
*Successfully overlaid CA trace in Paraview
+
*Submitted 2 new fwd sim tests
*Uploaded Study 15.12 maps to wiki, emailed group
+
*Looked into other ways of getting DOIs
 +
*Starting looking at potential journals for CyberShake technical papersskype:mashaliukis
  
 
== Today ==
 
== Today ==
*Check on BBP unit tests on Blue Waters
+
*Contact Scott Lathrop regarding Blue Waters or XSEDE accounts for UseIT
*Test new source from Dawei in forward sim
+
*Compare visualization results to Daniel's viz
*Look at getting DOI from USC or ISI
+
*Do some prep work for UseIT meeting Monday
 +
*Gather metrics from Study 15.12
  
 
== Blocked ==
 
== Blocked ==
Line 15: Line 17:
  
 
== Follow-ups ==
 
== Follow-ups ==
*None
+
*CyberShake call at 11
 +
*DB call at 12
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:19, 6 May 2016

Yesterday

  • BBP BBToolbox unit test failed on Blue Waters, will retry RC2
  • BBP acceptance tests passed
  • Workflow virtual summer school planning call, being asked to give intro
  • Submitted 2 new fwd sim tests
  • Looked into other ways of getting DOIs
  • Starting looking at potential journals for CyberShake technical papersskype:mashaliukis

Today

  • Contact Scott Lathrop regarding Blue Waters or XSEDE accounts for UseIT
  • Compare visualization results to Daniel's viz
  • Do some prep work for UseIT meeting Monday
  • Gather metrics from Study 15.12

Blocked

  • Change moment DB so all tables are MyISAM

Follow-ups

  • CyberShake call at 11
  • DB call at 12

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration