Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Created velocity plots along N-I fault surface
+
*Added CyberShake section to pegasus-mpi-cluster XSEDE paper
*EarthCube Workflow Workshop
+
*Repeated RWG/AWP comparison with CVM-H, looks good
*Compared RWG and AWP results from TEST with CVM-H - found Q issue, reran CVM-H job
+
*Reran AWP with CVM-S TEST site with modified Q - made mistake, running again
*Tested built find and zip, modified and changed workflow tools
+
*Checked on new TAU run on Kraken - need to rerun
*Submitted new TAU run on Kraken
+
*Monitor workflow run
 +
*Talked to Gideon - killing workflow, need to change cores/node
  
 
== Today ==
 
== Today ==
*Email out velocity plots along N-I surface for CVM-H/CVM-S
+
*Working on correctly specifying cores/node
*Add CyberShake section to pegasus-mpi-cluster XSEDE paper
+
*Add references to CyberShake section in paper
*Repeat RWG/AWP comparison with CVM-H
+
*Look at plots from AWP forward run if new CVM-S run still has ringing
*Rerun AWP with CVM-S TEST site with modified Q
 
*Look at plots from AWP forward run
 
 
*Add default striping change on Kraken dirs to workflow
 
*Add default striping change on Kraken dirs to workflow
*Check on new TAU run on Kraken
+
 
*Monitor workflow run
 
  
 
== Blocked ==
 
== Blocked ==

Revision as of 17:03, 17 April 2012

Yesterday

  • Added CyberShake section to pegasus-mpi-cluster XSEDE paper
  • Repeated RWG/AWP comparison with CVM-H, looks good
  • Reran AWP with CVM-S TEST site with modified Q - made mistake, running again
  • Checked on new TAU run on Kraken - need to rerun
  • Monitor workflow run
  • Talked to Gideon - killing workflow, need to change cores/node

Today

  • Working on correctly specifying cores/node
  • Add references to CyberShake section in paper
  • Look at plots from AWP forward run if new CVM-S run still has ringing
  • Add default striping change on Kraken dirs to workflow


Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration