Difference between revisions of "Staff Priorities - Fabio"

From SCECpedia
Jump to navigationJump to search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
  
* Posted new results
+
* Looked for obs data for NR event
* Completed work on attenuation plots code
+
** Forward station list table to CG
** Tested against Matlab version - matches results
+
* Mtg with CG regarding BBP issues
** Run for 5 BBP methods, posted results on bbpvault
+
* Site response changes
* Updated Pylint stats
+
** Surveyed current site response methods on BBP
 +
** Make available to all methods
  
 
== Today ==
 
== Today ==
  
* Work on code review slides
+
* Finish site response changes
* Additional metrics
+
** Maintain existing workflow
** Coverage for unit tests
+
** Need to run differently for GP/IRIKURA/SONG versus SDSU/UCSB/EXSIM
* Update Trac site
+
* Update wiki page for multi-segment ruptures
** Release notes page
+
** Add diagram
* Minor documentation updates
+
* Review High-F package from SA
  
 
== Blocked: ==
 
== Blocked: ==
Line 30: Line 31:
 
==== Broadband Platform ====
 
==== Broadband Platform ====
  
* Update GP rupture generator - Total: 3 days
+
* BBP Code updates needed before git migration
** Sent Rob parameters - done
+
** Move to argparse
** Integrate code - 1 day
+
** Simplify tests to use smaller files
** Run tests for Part-A / Part-B - 2 days
+
** Remove unused data files in tests directory
 
 
* Anderson GoF code from AS - Total: 3 days
 
** Analyze code, dependencies, provide AS feedback: 1 day
 
** Convert code to BBP module, add module to BBP workflow: 1 day
 
** Test BBP platform, produce new metrics: 1 day
 
 
 
* New BBToolbox version available from SDSU - Total: 3 days
 
** Incorporate SDSU changes into BBToolbox: 1 day
 
** Run Part-A/Part-B validations: 2 days
 
  
 
* NGA-West 2 validation on BBP - Total: 6 days
 
* NGA-West 2 validation on BBP - Total: 6 days
Line 49: Line 41:
 
** Run tests: 2 days
 
** Run tests: 2 days
 
** Review results: 2 days
 
** Review results: 2 days
 
* Setup laptop as EEW machine in software lab - Total: 1 day
 
** Erase laptop, install clean Mac OS X, install EEW software: 1 day
 
 
* Integrate Rupture Generator code from SG - Total: 28 days
 
** Review code, understand inputs/outputs, run outside platform: 1 day
 
** Run Part-A problem using Matlab code, review results: 1 day
 
** Migrate code into BBP Platform, convert Matlab code into Python/C/Fortran, test: 20 days
 
** Run Part-A/Part-B validation exercise on HPCC: 5 days (contingent on code performance)
 
 
==== High-F ====
 
 
* Set up High-F code repository - Total: 3 days
 
** Collect codes from groups, scripts - 1 day
 
** Select SVN/Github repository - 1 day
 
** Create repository - 1 day
 
 
* Understand how to map station location to grid point - Total: 2 days
 
** Understand approaches used by AWP and Hercules to map station location to grid point - 1 day
 
** Discuss with PM, DG, how to use UCVM to do this mapping - 1 day
 
  
 
=== Medium Term ===
 
=== Medium Term ===
Line 75: Line 47:
 
* New raytracing code for SDSU method
 
* New raytracing code for SDSU method
 
* Update Anderson method
 
* Update Anderson method
 +
* BBP Projects
 
* Try logging into Gordon
 
* 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