Difference between revisions of "Broadband Product Backlog"

From SCECpedia
Jump to navigationJump to search
Line 5: Line 5:
 
## 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
−
 
 
# UCSB
 
# UCSB
 
## Help implementation of UCSB double corner
 
## Help implementation of UCSB double corner
Line 15: Line 13:
 
## 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
Line 22: Line 19:
 
## 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)
−
 
 
# Future Release
 
# Future Release
 
## Define reduced set of tests for BBP verification before release
 
## Define reduced set of tests for BBP verification before release
 
## Document Science review process
 
## Document Science review process
−
## Document latest src/stl/vmod files/versions for the validation events
+
## Document latest src/stl/vmod files/versions for the validation events: include file in release
−
 
 
 
# Site effect modules
 
# Site effect modules
 
## 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
 
## Integrate Jeff Bayless site response module into BBP
−
 
 
# Other models
 
# Other models
 
## Refine and test Irikura Phase 2 modules
 
## Refine and test Irikura Phase 2 modules
Line 41: Line 35:
 
## Perform 1d test with GMM-consistent 1d profile
 
## 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)
 
## Update GP rupture generator to latest version from Arben (that changes slip distribution map to include asperities)
−
 
 
# Validation events
 
# Validation events
 
## Add more Part-A events to BBP Platform Validation
 
## Add more Part-A events to BBP Platform Validation

Revision as of 20:14, 3 October 2019

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