Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
 
*Blue Waters:
 
*Blue Waters:
**Finished SGT production runs!
+
**Looks like occasional I/O ops are very slow in seis_psa
**Ran test with seis_psa - looks like execution is taking 2/3 of runtime
+
*Ran curve sensitivity code
*Refactored curve sensitivity code to run much faster (fewer DB hits)
 
*Broadband production walkthrough with Fabio
 
 
*Continued scec-02 -> scec-04 data copy
 
*Continued scec-02 -> scec-04 data copy
  
 
== Today ==
 
== Today ==
 
*Blue Waters:
 
*Blue Waters:
**Get profiling info for seis_psa
+
**Get metrics from production SGTs
**Get stats for SGT production runs
 
 
*Stampede:
 
*Stampede:
**Work on offloading
+
**Submit failed PP runs
*Run curve sensitivity, get values for a single site, create ranking
+
*Check in on Broadband runs on epicenter
*Redo curve diff calculation since more have completed
 
 
*Continue scec-02 -> scec-04 data copy
 
*Continue scec-02 -> scec-04 data copy
*Monitor monitord population
+
*Analyze curve sensitivity results
  
 
== Blocked ==
 
== Blocked ==
Line 22: Line 18:
  
 
== Follow-ups ==  
 
== Follow-ups ==  
*Call with David
+
*Blue Waters
  
  

Revision as of 17:09, 20 May 2013

Yesterday

  • Blue Waters:
    • Looks like occasional I/O ops are very slow in seis_psa
  • Ran curve sensitivity code
  • Continued scec-02 -> scec-04 data copy

Today

  • 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

Blocked

  • No

Follow-ups

  • Blue Waters


Finish wiki entries for Stampede and Blue Waters validation

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration