Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Monitored Study 15.12 - looks like latest fix is working
+
*Monitor Study 15.12 - started clearing out DB entries
*Worked on debugging DirectSynth segfault - coming from MPI_Finalize and darshan
+
*Verified darshan is causing segfault with DirectSynth on Cori
*Worked with Dawei on segfaults - fixed segfault problem, now 0s and NaNs in output
+
*Resubmitted Cori workflow
 +
*Ran AWP test with homogeneous velocity mesh, still caused 0s and NaNs
 +
*Asked Kim for code to extract single points from source file
 +
*SC16 workshop rejected
  
 
== Today ==
 
== Today ==
*Produce map for C.B. Crouse
+
*Finish clearing DB entries for Study 15.12
*Monitor Study 15.12
+
*Verify workflow completed on Cori
*See if darshan is causing segfault (did something similar on Blue Waters)
+
*Try AWP run with single-point source
*Determine cause of 0s and NaNs in output
 
*Email Christine items for CyberShake call tomorrow
 
  
 
== Blocked ==
 
== Blocked ==
Line 15: Line 16:
  
 
== Follow-ups ==
 
== Follow-ups ==
*No
+
*CyberShake calls
 +
*Map for C.B. Crouse?
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:19, 25 March 2016

Yesterday

  • Monitor Study 15.12 - started clearing out DB entries
  • Verified darshan is causing segfault with DirectSynth on Cori
  • Resubmitted Cori workflow
  • Ran AWP test with homogeneous velocity mesh, still caused 0s and NaNs
  • Asked Kim for code to extract single points from source file
  • SC16 workshop rejected

Today

  • Finish clearing DB entries for Study 15.12
  • Verify workflow completed on Cori
  • Try AWP run with single-point source

Blocked

  • No

Follow-ups

  • CyberShake calls
  • Map for C.B. Crouse?

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration