Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Tried to generated CVM-H model for TEST site using CyberShake workflow on HPC - ran into workflow + UCVM issues
+
*Patrick helped sort out CVM-H issues on HPC - OOM problem
*Ran reciprocity with point source along Newport-Inglewood - still ringing, as expected
+
*Ran forward AWP-ODC with point source - error, resubmitted
*Got "good" version of forward AWP-ODC from Yifeng's SVN
+
*Ran AWP-ODC-SGT for TEST volume with CVM-H;  results seem better
*Started full CyberShake PP on Kraken - am documenting and improving performance issues
+
*Inserted hypocenters for RV4 into DB
  
 
== Today ==
 
== Today ==
*Finish debugging CyberShake issues on HPC
+
*Check that hypocenters were inserted
 +
*Email out reciprocity plots with TEST and CVM-H
 +
*Look at forward results when complete
 
*Monitor full CyberShake PP on Kraken
 
*Monitor full CyberShake PP on Kraken
*Run forward AWP-ODC with point source
 
*Run AWP-ODC-SGT with CVM-H when we get it
 
*Insert hypocenters for RV4 into DB
 
  
 
== Blocked ==
 
== Blocked ==
Line 16: Line 15:
  
 
== Follow-ups ==
 
== Follow-ups ==
*No
+
*CyberShake call
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:42, 11 April 2012

Yesterday

  • Patrick helped sort out CVM-H issues on HPC - OOM problem
  • Ran forward AWP-ODC with point source - error, resubmitted
  • Ran AWP-ODC-SGT for TEST volume with CVM-H; results seem better
  • Inserted hypocenters for RV4 into DB

Today

  • Check that hypocenters were inserted
  • Email out reciprocity plots with TEST and CVM-H
  • Look at forward results when complete
  • Monitor full CyberShake PP on Kraken

Blocked

  • No

Follow-ups

  • CyberShake call

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration