Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Refactored post-processing DAX generation code to include load-balancing,  
+
*Finish AWP PP run to get comparison hazard curves, emailed out
*Monitored AWP PP run; encountered Pegasus error with exitcode, Gideon checked in fix
+
*Updated Pegasus to get exitcode fix
*Selected 10 SGT sites to begin with for production run
+
*Tested script to update DB entries and RLS
 +
*Tested auto-submit of sites
 +
*Caught and fixed requested memory bug in refactored code
 +
*CyberShake calls
 +
*Outlined fields needed in seismogram header
  
 
== Today ==
 
== Today ==
*Look over papers for Liwen
+
*Respond to Efecan's question about CyberShake workflow jobs
*Finish AWP PP run to get comparison hazard curves
+
*Monitor execution of s022 to verify memory bug fix
*Update Pegasus to get exitcode fix
+
*Run hazard curves for additional verification sites
*Prepare 10 starting sites for SGT run
+
*Travel arrangements for SC12
  
 
== Blocked ==
 
== Blocked ==
Line 14: Line 18:
  
 
== Follow-ups ==
 
== Follow-ups ==
*CyberShake calls
+
*Phil - next steps for production run?
  
  
 
*Run test of I/O forwarding on Kraken
 
*Run test of I/O forwarding on Kraken
*Email CyberShake papers to Liwen
 
 
*Continue testing compiler optimizations
 
*Continue testing compiler optimizations
 
*Run some I/O tests to get reference values
 
*Run some I/O tests to get reference values

Revision as of 17:03, 27 September 2012

Yesterday

  • Finish AWP PP run to get comparison hazard curves, emailed out
  • Updated Pegasus to get exitcode fix
  • Tested script to update DB entries and RLS
  • Tested auto-submit of sites
  • Caught and fixed requested memory bug in refactored code
  • CyberShake calls
  • Outlined fields needed in seismogram header

Today

  • Respond to Efecan's question about CyberShake workflow jobs
  • Monitor execution of s022 to verify memory bug fix
  • Run hazard curves for additional verification sites
  • Travel arrangements for SC12

Blocked

  • No

Follow-ups

  • Phil - next steps for production run?


  • Run test of I/O forwarding on Kraken
  • Continue testing compiler optimizations
  • Run some I/O tests to get reference values


Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration