Difference between revisions of "Staff Priorities - Scott"

Revision as of 17:00, 24 May 2012

Continue investigating code to translate stresses to SGTs
CyberShake meetings
Looked at En-Jui's results, only 3 components - maybe velocity?
Submitted RWG and AWP simulations with just elastic model; AWP results were all NaNs

@@ Line 1: / Line 1: @@
 == Yesterday ==
-*Sent Kim point source results and point source code
+*Continue investigating code to translate stresses to SGTs
-*Sent En-Jui velocity mesh, fx_src, IN3D files to try test
+*CyberShake meetings
-*En-Jui and I seem to be on different pages, discuss in call today
+*Looked at En-Jui's results, only 3 components - maybe velocity?
-*Started looking at code to go from stresses to SGTs in both code bases
+*Submitted RWG and AWP simulations with just elastic model;  AWP results were all NaNs
 == Today ==
+*Try AWP run with xyn, xzn, yzn averaging commented out
+*Try fwd runs with double-couple source
 *Try hazard curve with JBSim3d_PSA
-*Continue investigating code to translate stresses to SGTs
+*Add memory hints to SGT generator
-*Get on the same page as En-Jui
+*Compile and test new pegasus-mpi-cluster
-*Test pegasus-mpi-cluster with memcached hook
-*Test pegasus-mpi-cluster with memory scheduling
-*Try RWG and AWP simulations with just elastic model
-*Try fwd runs with double-couple source
-*Try AWP run with xyn, xzn, yzn averaging commented out
 == Blocked ==
@@ Line 19: / Line 16: @@
 == Follow-ups ==
-*CyberShake meetings
 *Meeting with Phil?