Difference between revisions of "Staff Priorities - Fabio"

From SCECpedia
Jump to navigationJump to search
 
(334 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday: ==
+
== Yesterday ==
  
* Fling Study
+
* Looked for obs data for NR event
** Nothing to report today
+
** Forward station list table to CG
** We are now 39/42
+
* Mtg with CG regarding BBP issues
** Remaining scenarios all running on GEOSYS
+
* Site response changes
** Updated wiki tables: http://scec.usc.edu/scecpedia/Fling_Study#Codebase_URS.2FURS.2FURS.2FURS
+
** Surveyed current site response methods on BBP
* Trac #127: Survey BB Infrastructure: Closed.
+
** Make available to all methods
* Trac #102/#126 (dup): Move Plots code: Closed.
 
* Trac #130: File path length on SDSU code: Closed.
 
* Running full validation tests for URS code (NR, LP completed, LA almost done)
 
** Compared LP full validation of trunk and 11.2.3 and results are identical
 
** Running NR full validation on 11.2.3 (didn't save that output)
 
* Built trunk on HPCC
 
** PlotMap and PlotGOF didn't work with older matplotlib, created trac issues
 
* Started work on adapting run_bbp_parallel scripts to run Fling scenarios in 1 pass
 
  
== Today: ==
+
== Today ==
  
* Fling Study
+
* Finish site response changes
** Monitoring running scenarios
+
** Maintain existing workflow
* Compare URS full validations from trunk against 11.2.3 (LA and NR)
+
** Need to run differently for GP/IRIKURA/SONG versus SDSU/UCSB/EXSIM
* Continue working on HPCC parallel scripts to run Fling scenarios in half time
+
* Update wiki page for multi-segment ruptures
* Continue working on the testing framework
+
** Add diagram
* Work on Cruise Control setup (pending John Yu install)
+
* Review High-F package from SA
  
 
== Blocked: ==
 
== Blocked: ==
* John Yu: Installing Cruise Control
+
 
 +
* No
  
 
== Followups: ==
 
== Followups: ==
 +
 
* No
 
* No
  
== Ongoing: ==  
+
== To Do: ==
* Look for ways to break up the GF directory layout, some ideas are:
+
 
** Figure out how to separate the validation data from Greens Functions
+
=== Short Term ===
** Create separate validation package
+
 
** Separate events and codebases from each other
+
==== Broadband Platform ====
 +
 
 +
* BBP Code updates needed before git migration
 +
** Move to argparse
 +
** Simplify tests to use smaller files
 +
** Remove unused data files in tests directory
 +
 
 +
* NGA-West 2 validation on BBP - Total: 6 days
 +
** Contact CG, collect input scenarios: 1 day
 +
** Write test code: 1 day
 +
** Run tests: 2 days
 +
** Review results: 2 days
 +
 
 +
=== Medium Term ===
 +
 
 +
* Package GF generation code from RG into BBP Platform
 +
* New raytracing code for SDSU method
 +
* Update Anderson method
 +
* BBP Projects
 +
* Try logging into Gordon

Latest revision as of 17:48, 26 September 2016

Yesterday

  • Looked for obs data for NR event
    • Forward station list table to CG
  • Mtg with CG regarding BBP issues
  • Site response changes
    • Surveyed current site response methods on BBP
    • Make available to all methods

Today

  • Finish site response changes
    • Maintain existing workflow
    • Need to run differently for GP/IRIKURA/SONG versus SDSU/UCSB/EXSIM
  • Update wiki page for multi-segment ruptures
    • Add diagram
  • Review High-F package from SA

Blocked:

  • No

Followups:

  • No

To Do:

Short Term

Broadband Platform

  • BBP Code updates needed before git migration
    • Move to argparse
    • Simplify tests to use smaller files
    • Remove unused data files in tests directory
  • NGA-West 2 validation on BBP - Total: 6 days
    • Contact CG, collect input scenarios: 1 day
    • Write test code: 1 day
    • Run tests: 2 days
    • Review results: 2 days

Medium Term

  • Package GF generation code from RG into BBP Platform
  • New raytracing code for SDSU method
  • Update Anderson method
  • BBP Projects
  • Try logging into Gordon