Difference between revisions of "Broadband Product Backlog"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
* create a new dev branch to start working on | * create a new dev branch to start working on | ||
| + | * Create wiki list of validation events | ||
| + | |||
* 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 | ||
Revision as of 17:19, 10 June 2019
- create a new dev branch to start working on
- Create wiki list of validation events
- 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.
- move to python3
- add bbp github wiki list of validation events
- svm work for domniki
- change dev branch to bsd 3 license
- standard/common github continuous integration toos
- software coverage measurement tools (check with ossian).
- Update BBP license to the BSD-3 license
- Port the BBP to Python 3
- Integrate UCSB multi-fault rupture code
- 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
- Add multi-segment functionality to Irikura Recipe Method 2
- Add more Part-A events to BBP Platform Validation (L’Aquila, etc).
- Define reduced set of tests for BBP verification
- Document Science Review Process
- Integrate Sediment Velocity Model (SVM) site response module into BBP
- Integrate Pedro Arduino site effects module into BBP
