Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
 
*Blue Waters:
 
*Blue Waters:
**Added support for data movement when SGT jobs complete
+
**Tested RunManager integration, qsub dependencies, looks good, long queue times for SimSgt jobs
 
*Stampede:
 
*Stampede:
**Followed up with GRAM group - can't look at it until next week
+
**Started post-processing on first set of WNGC SGTs
**Wrote cron job to kill job-managers*Complete wiki entries for Blue Waters and Stampede validation
+
*Reworked run scripts on shock and DAX generator to support post-processing the same site with multiple runs simultaneously
*Emailed Phil forward seismogram overlays
+
*Calculated peak amplitudes for Rob and emailed
*Emailed David path to PSA code with example
+
*CyberShake calls
  
 
== Today ==
 
== Today ==
 
*Blue Waters:
 
*Blue Waters:
**Test RunManager integration, data movement, qsub dependencies
+
**Test data movement, monitor run
 
*Stampede:
 
*Stampede:
**Post-process 4 sets of WNGC SGTs (test support for multiple runs with same site, cron job)
+
**Post-process 3 sets of WNGC SGTs
*Email forward seismogram overlays to the CyberShake group
+
**Watch JM killer
  
 
== Blocked ==
 
== Blocked ==
Line 19: Line 19:
  
 
== Follow-ups ==  
 
== Follow-ups ==  
*CyberShake calls
+
*SEISM call at 11
  
  

Revision as of 17:06, 14 March 2013

Yesterday

  • Blue Waters:
    • Tested RunManager integration, qsub dependencies, looks good, long queue times for SimSgt jobs
  • Stampede:
    • Started post-processing on first set of WNGC SGTs
  • Reworked run scripts on shock and DAX generator to support post-processing the same site with multiple runs simultaneously
  • Calculated peak amplitudes for Rob and emailed
  • CyberShake calls

Today

  • Blue Waters:
    • Test data movement, monitor run
  • Stampede:
    • Post-process 3 sets of WNGC SGTs
    • Watch JM killer

Blocked

  • No

Follow-ups

  • SEISM call at 11


Email ISI to ask about gathering metrics from Study 2.2 Think about readiness review Think about access to CyberShake data

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration