Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Calculated rupture-site distance, added new DB column
+
*Worked with John to post BB files for Maren on hypocenter
*Continued work on pegasus-statistics issues, got updated versions from ISI
+
*Retried PMC run, 10x480 w/hierarchy - found bug
*Error with PMC run, 10x480 w/hierarchy test; updated pegasus on Kraken
+
*Tried to update monitord DB, ran into mysql error
*Continued work on debugging weird AWP results, isolating problem change
+
*Tried new PP workfow to test monitord, insertion errors, something fishy in PSA files
*Emailed Rob to check on correct version of emod3d-mpi for runs
+
*Continued work with AWP/RWG, isolated issue, try with surface source
 +
*CyberShake calls
  
 
== Today ==
 
== Today ==
*Populate DB with rupture-site info
+
*Check on rupture-site distance population
*Retry PMC run, 10x480 w/hierarchy
+
*Fix hierarchy bug, rerun
*Update Pegasus, try monitord again - Pegasus group would like results before 4.1 release
+
*Check on SGTs used in large PSA files - think from full run.  Check past full runs.
 +
*Email Yifeng's student paths to CyberShake executables
  
 
== Blocked ==
 
== Blocked ==
*Hypocenter login issues, so can't post new results for Maren - ping John again
+
*No
  
 
== Follow-ups ==
 
== Follow-ups ==
*CyberShake calls
+
*No
  
  

Revision as of 17:10, 23 August 2012

Yesterday

  • Worked with John to post BB files for Maren on hypocenter
  • Retried PMC run, 10x480 w/hierarchy - found bug
  • Tried to update monitord DB, ran into mysql error
  • Tried new PP workfow to test monitord, insertion errors, something fishy in PSA files
  • Continued work with AWP/RWG, isolated issue, try with surface source
  • CyberShake calls

Today

  • Check on rupture-site distance population
  • Fix hierarchy bug, rerun
  • Check on SGTs used in large PSA files - think from full run. Check past full runs.
  • Email Yifeng's student paths to CyberShake executables

Blocked

  • No

Follow-ups

  • No


  • Runs for Rob and Kim
  • Continue testing compiler optimizations
  • Run some I/O tests to get reference values


Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration