Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Continued testing new version of JBSim3d
+
*Tried PP workflow with new JBSim3d - lots of seg faults
*Checked on AWP forward run, got OOM errors - asked Yifeng for help
+
*Edited workflow paper (Word version)
*Checked on s351 workflow run, calculated some PP metrics - error, waiting on fix for better ones
+
*Read AWP document from Yifeng about source, tried again, still problems - need binary file
 +
*ISI fixed statistics issue, look over stats from full run
 +
*Submitted Z component runs
  
 
== Today ==
 
== Today ==
*Try PP workflow with new JBSim3d
+
*Debug seg faults, try again
*Edit workflow paper (Word version)
+
*Create binary input and resubmit source partitioning
*Read AWP document from Yifeng about source, make adjustments
+
*If source partitioning succeeds, resubmit forward run
*Queue up new suggested runs from Kim and Rob
+
*Check on Z component runs
 +
*Set up and submit halfspace runs
  
 
== Blocked ==
 
== Blocked ==
Line 14: Line 17:
  
 
== Follow-ups ==
 
== Follow-ups ==
*No
+
*CyberShake call
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:05, 2 May 2012

Yesterday

  • Tried PP workflow with new JBSim3d - lots of seg faults
  • Edited workflow paper (Word version)
  • Read AWP document from Yifeng about source, tried again, still problems - need binary file
  • ISI fixed statistics issue, look over stats from full run
  • Submitted Z component runs

Today

  • Debug seg faults, try again
  • Create binary input and resubmit source partitioning
  • If source partitioning succeeds, resubmit forward run
  • Check on Z component runs
  • Set up and submit halfspace runs

Blocked

  • No

Follow-ups

  • CyberShake call

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration