Difference between revisions of "Staff Priorities - Fabio"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday: ==
 
== Yesterday: ==
  
* Finished draft for AGU abstract, sent for comments
+
* Tested SDSU MOGoF code with gfortran
* Ran full NR validation with 133 stations
+
** Results match ifort, code checked into svn
** Got good result
+
* Fixed race condition on hpcc between multiple realizations using matplotlib
* Contacted KW wrt SWUS scenario simulations
+
** BBP now created temp directories so that each realization has its own matplotlib's cache file
** Scheduled follow-up today
+
* Call with RG about NoCal GFs, and seismogram's durations
* Ran test cases for JB
+
** Ran SDSU code with 325s duration -- ran fine
** Some issues with UCSB code
+
** Ran SDSU code with 409s duration and changed Respect array sizes -- still running
 +
* Got Splay Fault scenarios from KW
 +
** Updated table with mode descriptions
 +
** Added new scenarios
  
 
== Today: ==
 
== Today: ==
  
* Set up Loma Prieta full validation
+
* Finish SDSU 409s run and send results to KO and RG for comparison
* Run Loma Prieta full validation for GP
+
* Start SDSU simple fault runs after getting 'ok'
* Run NR full validation for ExSIM, SDSU, CSM
+
* Start full validations for CSM and UCSB codes
* Finalize AGU abstract after all comments are in
+
* Work on gfortran conversion for SDSU site response module
* Continue debugging UCSB code issue from JB
+
* Start GP and EXSIM runs for splay faults
  
 
== Blocked: ==
 
== Blocked: ==
Line 21: Line 24:
  
 
== Followups: ==
 
== Followups: ==
* KW - SWUS scenarios @ 3:00pm
+
* Cybershake calls @ 11:00

Revision as of 17:41, 14 August 2013

Yesterday:

  • Tested SDSU MOGoF code with gfortran
    • Results match ifort, code checked into svn
  • Fixed race condition on hpcc between multiple realizations using matplotlib
    • BBP now created temp directories so that each realization has its own matplotlib's cache file
  • Call with RG about NoCal GFs, and seismogram's durations
    • Ran SDSU code with 325s duration -- ran fine
    • Ran SDSU code with 409s duration and changed Respect array sizes -- still running
  • Got Splay Fault scenarios from KW
    • Updated table with mode descriptions
    • Added new scenarios

Today:

  • Finish SDSU 409s run and send results to KO and RG for comparison
  • Start SDSU simple fault runs after getting 'ok'
  • Start full validations for CSM and UCSB codes
  • Work on gfortran conversion for SDSU site response module
  • Start GP and EXSIM runs for splay faults

Blocked:

  • No

Followups:

  • Cybershake calls @ 11:00