Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Tried PP workflow with new JBSim3d - lots of seg faults
+
*Couldn't replicate seg faults, tried full-scale, repeated;  tracked down to corruption in Y extracted SGTs
*Edited workflow paper (Word version)
+
*Submitted source partitioning job
*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
 
*Submitted Z component runs
 +
*Submitted halfspace runs
 +
*Plotted and sent other sets of AWP/RWG seismograms from TEST hazard curve
 +
*Responded to Rob re:MPI_Sendrecv()
  
 
== Today ==
 
== Today ==
*Debug seg faults, try again
+
*Continue debugging seg faults
*Create binary input and resubmit source partitioning
+
*Generate list of metrics to produce from Kraken runs
*If source partitioning succeeds, resubmit forward run
+
*When Kraken returns, check on queued runs
*Check on Z component runs
 
*Set up and submit halfspace runs
 
*Look over paper again
 
*Generate list of metrics
 
*Pull out and plot other sets of AWP/RWG seismograms from TEST hazard curve
 
  
 
== Blocked ==
 
== Blocked ==
*No
+
*Kraken down for PM
  
 
== Follow-ups ==
 
== Follow-ups ==
*CyberShake call
+
*No
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:04, 3 May 2012

Yesterday

  • Couldn't replicate seg faults, tried full-scale, repeated; tracked down to corruption in Y extracted SGTs
  • Submitted source partitioning job
  • Submitted Z component runs
  • Submitted halfspace runs
  • Plotted and sent other sets of AWP/RWG seismograms from TEST hazard curve
  • Responded to Rob re:MPI_Sendrecv()

Today

  • Continue debugging seg faults
  • Generate list of metrics to produce from Kraken runs
  • When Kraken returns, check on queued runs

Blocked

  • Kraken down for PM

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration