Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Run BBP unit tests on RC2 - 1 test failed
+
*Finished modifying DB
*Regenerated viz with velocity model boxes, revised scaling
+
*Added Study start/end times to DB
*Visualized run with v1.2 partitioning - small differences but nothing major
+
*Submitted job to create velocity model for statewide 1 Hz SGT run
*Updated the DB so that the new Study table is integrated
+
*Changed Vp ceiling to 9500 m/s
*Started cleaning up and migrating old runs to the correct Study and Hazard Dataset
 
  
 
== Today ==
 
== Today ==
*Finish modifying DB
+
*Create slides for UGMS meeting
*Add Study start/end times to DB
+
*Continue work on statewide 1 Hz SGT run
 
*Gather metrics from Study 15.12
 
*Gather metrics from Study 15.12
 
*Document details of stochastic sims in Study 15.12 on wiki
 
*Document details of stochastic sims in Study 15.12 on wiki
 
*Draft DB migration procedure
 
*Draft DB migration procedure
 
*Document and put into version control tools for creating viz
 
*Document and put into version control tools for creating viz
*Create velocity model for statewide 1 Hz SGT run
 
*Remove and rebuild code without Vp ceiling
 
*Create slides for UGMS meeting
 
  
 
== Blocked ==
 
== Blocked ==
Line 21: Line 17:
  
 
== Follow-ups ==
 
== Follow-ups ==
*Intern call at 1 pm
+
*CyberShake calls at 11
  
 
== Areas of Responsibilities ==
 
== Areas of Responsibilities ==

Revision as of 17:18, 13 May 2016

Yesterday

  • Finished modifying DB
  • Added Study start/end times to DB
  • Submitted job to create velocity model for statewide 1 Hz SGT run
  • Changed Vp ceiling to 9500 m/s

Today

  • Create slides for UGMS meeting
  • Continue work on statewide 1 Hz SGT run
  • Gather metrics from Study 15.12
  • Document details of stochastic sims in Study 15.12 on wiki
  • Draft DB migration procedure
  • Document and put into version control tools for creating viz

Blocked

  • No

Follow-ups

  • CyberShake calls at 11

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration