Difference between revisions of "Broadband Product Backlog"

From SCECpedia
Jump to navigationJump to search
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
== Pending tasks ==
 +
 
# Core
 
# Core
 +
## Update BBP Platform to use current compilers
 
## Update BBP license to the BSD-3 license
 
## Update BBP license to the BSD-3 license
 
# UCSB
 
# UCSB
Line 11: Line 14:
 
## 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
−
## standard/common github continuous integration toos
+
## standard/common github continuous integration tools
 
## software coverage measurement tools (check with ossian)
 
## software coverage measurement tools (check with ossian)
 
# Future Release
 
# Future Release
Line 22: Line 25:
 
## Integrate Jeff Bayless site response module into BBP
 
## Integrate Jeff Bayless site response module into BBP
 
# Other models
 
# Other models
 +
## Work with SDSU team to debug LF timeseries duration differences in the SDSU method
 +
## Support SDSU frequency-dependent spatial correlation integration with the BBP
 
## Refine and test Irikura Phase 2 modules
 
## 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
 
## Update multi-segment approach for GP and SDSU to compute seismograms in one simulation like Song and Irikura Method 1
Line 40: Line 45:
 
## Start FAS-based validation
 
## Start FAS-based validation
  
−
# BBP Sprint
+
== Previous Sprints ==
−
## June 10th - July 31st
+
 
 +
=== 2020-02-01 - 2020-02-29 - BBP Sprint ===
 +
 
 +
# Create Northridge BBP simulation using the GP method and including complete set of data products
 +
## Share results with CG
 +
# Run Landers and Hector Mine with GP and SDSU methods
 +
## Use both Mojave500 and Southern Sierra Nevada GFs
 +
## Share results with BBP group
 +
 
 +
=== 2019-10-03 - 2019-10-31 - BBP Sprint ===
 +
 
 +
# Troubleshoot and finalize Vs30-based SVM site response module (verification)
 +
## Done: Evaluate with all methods, user selects which site response module to use in simulation
 +
## Done: Run all Part-A events and compare GP2014 and VS30 SeismoSoil results, share with modelers
 +
# Support UCSB improvements to their method
 +
## Double corner, average rupture velocity rules
 +
## Done: Re-run Part-A events
 +
# Continue validation event: L'Aquila
 +
## Done: SRC/STL files, velocity model for all methods, with GFs and region parameters, all packaged for release
 +
## Done: Run all methods, share results with groups, receive approval nod from each group
 +
# Update Part-A validation packages with latest version from CG with updated Vs30s
 +
## Done: Run Part-A validation for all methods/events, share results with CG, do not expect big changes
 +
# Background: Update GP method to run multi-segment ruptures in a single pass
 +
## Done: Run 3-segment Landers using new approach, compare results with previous runs
 +
 
 +
=== 2019-06-10 - 2019-07-31 - BBP Sprint ===
 +
 
 
## Python 3 *** Done: Working with Python 3.6
 
## Python 3 *** Done: Working with Python 3.6
 
## SVM
 
## SVM
Line 56: Line 87:
 
## Backup: Start variability implementation using GP
 
## Backup: Start variability implementation using GP
  
−
# Completed in Summer 2019 Sprint
+
=== Completed in Summer 2019 Sprint ===
 +
 
 
## 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
Line 62: Line 94:
 
## Port the BBP to Python 3
 
## Port the BBP to Python 3
 
## Validation event : Hector Mine
 
## Validation event : Hector Mine
 +
 +
== Tasks required for next BBP release ==
  
 
# BBP Release
 
# BBP Release

Latest revision as of 17:58, 18 March 2020

Pending tasks

  1. Core
    1. Update BBP Platform to use current compilers
    2. Update BBP license to the BSD-3 license
  2. 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
  3. 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 tools
    5. software coverage measurement tools (check with ossian)
  4. 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
  5. 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
  6. Other models
    1. Work with SDSU team to debug LF timeseries duration differences in the SDSU method
    2. Support SDSU frequency-dependent spatial correlation integration with the BBP
    3. Refine and test Irikura Phase 2 modules
    4. Update multi-segment approach for GP and SDSU to compute seismograms in one simulation like Song and Irikura Method 1
    5. Draping rupture over complex faults in GP method
    6. GP (and potentially others) variability study in SRC (fault dimensions, magnitude, etc.)
    7. Add multi-segment functionality to Irikura Recipe Method 2
    8. Perform 1d test with GMM-consistent 1d profile
    9. Update GP rupture generator to latest version from Arben (that changes slip distribution map to include asperities)
  7. 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

Previous Sprints

2020-02-01 - 2020-02-29 - BBP Sprint

  1. Create Northridge BBP simulation using the GP method and including complete set of data products
    1. Share results with CG
  2. Run Landers and Hector Mine with GP and SDSU methods
    1. Use both Mojave500 and Southern Sierra Nevada GFs
    2. Share results with BBP group

2019-10-03 - 2019-10-31 - BBP Sprint

  1. Troubleshoot and finalize Vs30-based SVM site response module (verification)
    1. Done: Evaluate with all methods, user selects which site response module to use in simulation
    2. Done: Run all Part-A events and compare GP2014 and VS30 SeismoSoil results, share with modelers
  2. Support UCSB improvements to their method
    1. Double corner, average rupture velocity rules
    2. Done: Re-run Part-A events
  3. Continue validation event: L'Aquila
    1. Done: SRC/STL files, velocity model for all methods, with GFs and region parameters, all packaged for release
    2. Done: Run all methods, share results with groups, receive approval nod from each group
  4. Update Part-A validation packages with latest version from CG with updated Vs30s
    1. Done: Run Part-A validation for all methods/events, share results with CG, do not expect big changes
  5. Background: Update GP method to run multi-segment ruptures in a single pass
    1. Done: Run 3-segment Landers using new approach, compare results with previous runs

2019-06-10 - 2019-07-31 - BBP Sprint

    1. Python 3 *** Done: Working with Python 3.6
    2. SVM
      1. Done: Vs30-only implementation
      2. Done: available with all methods
      3. Done: validated with Part-A events (TBD by CG)
    3. Check UCSB availability
      1. Done: Schedule work for multi-segment, double corner, variable-spacing
    4. Continue adding validation events
      1. Done: Operations, running simulations
      2. Done: Part-A events as available from science teams
      3. Done: Add new regions as needed by new Part-A events
    5. Backup: Improve UCSB method (multi-segments/variable spacing)
    6. Backup: Start variability implementation using GP

Completed in Summer 2019 Sprint

    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

Tasks required for next BBP release

  1. BBP Release
    1. Multi-segment Irikura 2
    2. UCSB multi-segment and variable spacing for smaller GFs
    3. New site-effects module (SVM)
    4. Python 3
    5. UCSB
Retrieved from "https://strike.scec.org/scecwiki/index.php?title=Broadband_Product_Backlog&oldid=24064"