Difference between revisions of "Broadband Product Backlog"

From SCECpedia
Jump to navigationJump to search
Line 2: Line 2:
 
** 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
 +
** Port the BBP to Python 3
 +
** Validation event : Hector Mine
  
 
* Core
 
* Core
−
** Port the BBP to Python 3
 
 
** Update BBP license to the BSD-3 license
 
** Update BBP license to the BSD-3 license
  
Line 10: Line 12:
 
** Help implementation of UCSB double corner
 
** Help implementation of UCSB double corner
 
** Implement variable spacing for smaller GFs
 
** Implement variable spacing for smaller GFs
 +
** Convert rupture generator output to SRF format, add plots
 
** Integrate UCSB multi-fault rupture code
 
** Integrate UCSB multi-fault rupture code
 
*** Start with Landers
 
*** Start with Landers
  
 
* Infrastructure
 
* Infrastructure
−
** talk with edric about the assets tracking
+
** Talk with Edric about the assets tracking
−
** look at what file we can use to track bbp installs
+
** 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
+
** Ask Edric about google analytics information about scec.org/research/bbp or scecpedia/Broadband_Platform or any other google analytics we have
−
** add bbp github wiki list of validation events
 
 
** standard/common github continuous integration toos
 
** standard/common github continuous integration toos
 
** software coverage measurement tools (check with ossian)
 
** software coverage measurement tools (check with ossian)
Line 28: Line 30:
 
** Integrate Sediment Velocity Model (SVM) site response module into BBP
 
** Integrate Sediment Velocity Model (SVM) site response module into BBP
 
** Integrate Pedro Arduino site effects module into BBP
 
** Integrate Pedro Arduino site effects module into BBP
 +
** Integrate Jeff Bayless site response module into BBP
  
 
* Other models
 
* Other models
Line 39: Line 42:
 
* Validation events
 
* Validation events
 
** Add more Part-A events to BBP Platform Validation
 
** Add more Part-A events to BBP Platform Validation
−
*** Hector Mine
 
 
*** L’Aquila
 
*** L’Aquila
 
*** Christchurch
 
*** Christchurch

Revision as of 17:03, 3 October 2019

  • 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
  • Core
    • Update BBP license to the BSD-3 license
  • 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
  • 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)
  • Future Release
    • Define reduced set of tests for BBP verification before release
    • Document Science review process
  • 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
  • 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
  • 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
  • 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
Retrieved from "https://strike.scec.org/scecwiki/index.php?title=Broadband_Product_Backlog&oldid=23283"