Difference between revisions of "Broadband Product Backlog"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
# Done
 
# Done
** Create a new dev branch to start working on
+
##** Create a new dev branch to start working on
** Create wiki list of validation events
+
##** Create wiki list of validation events
** add bbp github wiki list of validation events
+
##** add bbp github wiki list of validation events
** Port the BBP to Python 3
+
##** Port the BBP to Python 3
** Validation event : Hector Mine
+
##** Validation event : Hector Mine
 
# Core
 
# Core
 
** Update BBP license to the BSD-3 license
 
** Update BBP license to the BSD-3 license

Revision as of 19:59, 3 October 2019

  1. Done
        • Create a new dev branch to start working on
        • Create wiki list of validation events
        • add bbp github wiki list of validation events
        • Port the BBP to Python 3
        • Validation event : Hector Mine
  2. Core
    • Update BBP license to the BSD-3 license
  1. UCSB
    • Help implementation of UCSB double corner
    • Implement variable spacing for smaller GFs
    • Convert rupture generator output to SRF format, add plots
    • Integrate UCSB multi-fault rupture code
      • Start with Landers
  1. Infrastructure
    • Talk with Edric about the assets tracking
    • Look at what file we can use to track bbp installs
    • Ask Edric about google analytics information about scec.org/research/bbp or scecpedia/Broadband_Platform or any other google analytics we have
    • standard/common github continuous integration toos
    • software coverage measurement tools (check with ossian)
  1. Future Release
    • Define reduced set of tests for BBP verification before release
    • Document Science review process
  1. Site effect modules
    • Integrate Sediment Velocity Model (SVM) site response module into BBP
    • Integrate Pedro Arduino site effects module into BBP
    • Integrate Jeff Bayless site response module into BBP
  1. Other models
    • Refine and test Irikura Phase 2 modules
    • Update multi-segment approach for GP and SDSU to compute seismograms in one simulation like Song and Irikura Method 1
    • Draping rupture over complex faults in GP method
    • GP (and potentially others) variability study in SRC (fault dimensions, magnitude, etc.)
    • Add multi-segment functionality to Irikura Recipe Method 2
    • Perform 1d test with GMM-consistent 1d profile
    • Update GP rupture generator to latest version from Arben (that changes slip distribution map to include asperities)
  1. Validation events
    • Add more Part-A events to BBP Platform Validation
      • L’Aquila
      • Christchurch
      • Chi Chi
      • Koaceli
      • El Mayor
      • Darfield
    • Implement japanese GMPEs (Hiroe's e-mail from 2018-10-30)
    • Start FAS-based validation
  1. BBP Sprint
    • June 10th - July 31st
    • Python 3
      • Done: Working with Python 3.6
    • SVM
      • Done: Vs30-only implementation
      • Done: available with all methods
      • Done: validated with Part-A events (TBD by CG)
    • Check UCSB availability
      • Done: Schedule work for multi-segment, double corner, variable-spacing
    • Continue adding validation events
      • Done: Operations, running simulations
      • Done: Part-A events as available from science teams
      • Done: Add new regions as needed by new Part-A events
    • Backup: Improve UCSB method (multi-segments/variable spacing)
    • Backup: Start variability implementation using GP
  • BBP Release
    • Multi-segment Irikura 2
    • UCSB multi-segment and variable spacing for smaller GFs
    • New site-effects module (SVM)
    • Python 3
    • UCSB