Difference between revisions of "Staff Priorities - Scott"

Revision as of 19:16, 25 April 2012

SRF staging completed, resubmitted workflow on Kraken
Ran seismograms by hand with AWP and RWG, investigated big differences - was using wrong SGT X file
Continued development of JBSim3d + memcached + in-mem RV + PSA calculation
Did performance review preparation

Consider different filtering with RWG code - explain difference in PSA values?
Continued development of JBSim3d + memcached + in-mem RV + PSA calculation (need to refactor)
Monitor LGU PP workflow on Kraken

@@ Line 1: / Line 1: @@
 == Yesterday ==
-*Attended Python workshop run by TACC
+*SRF staging completed, resubmitted workflow on Kraken
-*Found more memory issues on Kraken.  Explored and discovered some of the SRFs are corrupt (hence asking for weird quantities of memory)
+*Ran seismograms by hand with AWP and RWG, investigated big differences - was using wrong SGT X file
-*Started Globus Online job to transfer corrupt files (based on md5)
+*Continued development of JBSim3d + memcached + in-mem RV + PSA calculation
-*Calculated hazard curve with AWP SGTs - lower (high-PSA variations lower by 4x).  Running some seismograms by hand.
+*Did performance review preparation
 == Today ==
-*When SRF staging completes, rerun workflow on Kraken
+*Consider different filtering with RWG code - explain difference in PSA values?
-*Run seismograms by hand with AWP and RWG, investigate big differences
+*Continued development of JBSim3d + memcached + in-mem RV + PSA calculation (need to refactor)
-*Continue development of JBSim3d + memcached + in-mem RV + PSA calculation
+*Monitor LGU PP workflow on Kraken
-*Ponder way to reduce number of seismogram files
+*
-*Performance review
 == Blocked ==
@@ Line 16: / Line 15: @@
 == Follow-ups ==
-*No
+*CyberShake call
+*Performance review with Phil
 == Areas of Responsibilities ==