Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Caught up on email
+
*Continued work on failed CyberShake runs - got more to complete
*Started looking at failed CyberShake PP runs
+
*Emailed out basic metrics from production runs
*May have fixed wireless card issues
+
*Resumed scec-02 -> scec-04 copy
  
 
== Today ==
 
== Today ==
*Continue work on failed CyberShake runs - loosen up allowed values, especially at high periods
+
*Continue scec-02 copy
*Metrics from production runs
+
*Mine for more complex SGT metrics
*Resume scec-02 -> scec-04 copy
+
*Email Omar about filled up quota
 +
*Update LoadAmps check, rerun workflows
  
 
== Blocked ==
 
== Blocked ==
Line 13: Line 14:
  
 
== Follow-ups ==  
 
== Follow-ups ==  
*No
+
*CyberShake calls
 +
*John Yu
  
 
Finish wiki entries for Stampede and Blue Waters validation
 
Finish wiki entries for Stampede and Blue Waters validation

Revision as of 17:23, 12 June 2013

Yesterday

  • Continued work on failed CyberShake runs - got more to complete
  • Emailed out basic metrics from production runs
  • Resumed scec-02 -> scec-04 copy

Today

  • Continue scec-02 copy
  • Mine for more complex SGT metrics
  • Email Omar about filled up quota
  • Update LoadAmps check, rerun workflows

Blocked

  • No

Follow-ups

  • CyberShake calls
  • John Yu

Finish wiki entries for Stampede and Blue Waters validation

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration
  • Blue Waters:
    • Get metrics from production SGTs
  • Stampede:
    • Submit failed PP runs
  • Check in on Broadband runs on epicenter
  • Continue scec-02 -> scec-04 data copy
  • Analyze curve sensitivity results