Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Responded to Marine
+
*Checked on Rupture Variation inserts for ERF 36 - continuing, slowly
*Continued inserting RuptureVariation entries for ERF 36
+
*Tried to run pegasus-statistics on Study 2.2 results, asked John to upgrade Python on aftershock
*Integrated workflow passes on Stampede
+
*Tested 1 Hz CyberShake velocity modifications - small test passed
*Emailed TACC for help with tera3d account
+
*Added job id update job to Integrated workflow and test
*Worked on UCVM improvements for 1 Hz
+
*Tried to test of integrated workflow on Blue Waters with scottcal proxy - asked John to upgrade to unlimited strength jars
  
 
== Today ==
 
== Today ==
*Check on Rupture Variation inserts for ERF 36
+
*Try medium and large CyberShake velocity tests
*Run pegasus-statistics on Study 2.2 results
+
*Test proxy when jars are upgraded
*Test 1 Hz CyberShake velocity modifications
+
*Run pegasus-statistics when upgraded
*Add job id update job to Integrated workflow and test
+
*Look over Maren's CyberShake paper
*Begin tests of integrated workflow on Blue Waters with scottcal proxy
+
*Monitor Rupture Variation inserts
 +
*Continue with 1 Hz modifications to SGT workflow
  
 
== Blocked ==
 
== Blocked ==
Line 17: Line 18:
  
 
== Follow-ups ==  
 
== Follow-ups ==  
*No
+
*CyberShake calls
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:14, 21 August 2013

Yesterday

  • Checked on Rupture Variation inserts for ERF 36 - continuing, slowly
  • Tried to run pegasus-statistics on Study 2.2 results, asked John to upgrade Python on aftershock
  • Tested 1 Hz CyberShake velocity modifications - small test passed
  • Added job id update job to Integrated workflow and test
  • Tried to test of integrated workflow on Blue Waters with scottcal proxy - asked John to upgrade to unlimited strength jars

Today

  • Try medium and large CyberShake velocity tests
  • Test proxy when jars are upgraded
  • Run pegasus-statistics when upgraded
  • Look over Maren's CyberShake paper
  • Monitor Rupture Variation inserts
  • Continue with 1 Hz modifications to SGT workflow

Blocked

  • No

Follow-ups

  • CyberShake calls

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration