Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Reran AWP SGTs on Kraken with correct mesh specification, looking better
+
*Retried AWP post-processing on Kraken - non-zero return code, possibly an accident?
*Investigated UCVM issue - difference in model coordinates file due to floats
+
*CyberShake calls - Pegasus group working on non-GRAM solutions to remote job submission
 +
*Installed and test AWP on BW - waiting on Kraken results to perform validation
 +
*Installed SGT codes on Stampede, tested through PreSGT - seg fault
 +
*Followed up with TACC staff - learned GridFTP server, possibly GRAM gatekeeper
  
 
== Today ==
 
== Today ==
*Move ahead with AWP post-processing on Kraken
+
*Continue testing AWP post-processing on Kraken
*Install and test AWP on BW
+
*Debug gen_sgtgrid seg fault on Stampede
*Install SGT codes on Stampede
+
*Experiment with GRAM gatekeeper on Stampede, if available
  
 
== Blocked ==
 
== Blocked ==
Line 12: Line 15:
  
 
== Follow-ups ==
 
== Follow-ups ==
*CyberShake calls
+
*No
  
  

Revision as of 18:08, 31 January 2013

Yesterday

  • Retried AWP post-processing on Kraken - non-zero return code, possibly an accident?
  • CyberShake calls - Pegasus group working on non-GRAM solutions to remote job submission
  • Installed and test AWP on BW - waiting on Kraken results to perform validation
  • Installed SGT codes on Stampede, tested through PreSGT - seg fault
  • Followed up with TACC staff - learned GridFTP server, possibly GRAM gatekeeper

Today

  • Continue testing AWP post-processing on Kraken
  • Debug gen_sgtgrid seg fault on Stampede
  • Experiment with GRAM gatekeeper on Stampede, if available

Blocked

  • No

Follow-ups

  • No


  • Watch Morgan's AGU presentation
  • Reply to TACC, NICS regarding authorized people

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration