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
+
* Done
* Create wiki list of validation events
+
** Create a new dev branch to start working on
 +
** Create wiki list of validation events
  
* talk with edric about the assets tracking
+
* Core
* look at what file we can use to track bbp installs
+
** Port the BBP to Python 3
* ask edric about google analytics information about scec.org/research/bbp or scecpedia/Broadband_Platform or any other google analytics we have.
+
** Update BBP license to the BSD-3 license
* 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
+
* UCSB
* Port the BBP to Python 3
+
** Help implementation of UCSB double corner
* Integrate UCSB multi-fault rupture code
+
** Implement variable spacing for smaller GFs
* Refine and test Irikura Phase 2 modules
+
** Integrate UCSB multi-fault rupture code
* Update multi-segment approach for GP and SDSU to compute seismograms in one simulation like Song and Irikura Method 1
+
*** Start with Landers
* Add multi-segment functionality to Irikura Recipe Method 2  
+
 
* Add more Part-A events to BBP Platform Validation (L’Aquila, etc).
+
* Infrastructure
* Define reduced set of tests for BBP verification
+
** talk with edric about the assets tracking
* Document Science Review Process
+
** look at what file we can use to track bbp installs
* Integrate Sediment Velocity Model (SVM) site response module into BBP
+
** ask edric about google analytics information about scec.org/research/bbp or scecpedia/Broadband_Platform or any other google analytics we have.
* Integrate Pedro Arduino site effects module into BBP
+
** add bbp github wiki list of validation events
 +
** standard/common github continuous integration toos
 +
** software coverage measurement tools (check with ossian).
 +
** Define reduced set of tests for BBP verification
 +
** 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
 +
 
 +
* 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
 +
** Add multi-segment functionality to Irikura Recipe Method 2  
 +
 
 +
* Validation events
 +
** Add more Part-A events to BBP Platform Validation (L’Aquila, etc)

Revision as of 17:27, 10 June 2019

  • Done
    • Create a new dev branch to start working on
    • Create wiki list of validation events
  • Core
    • Port the BBP to Python 3
    • Update BBP license to the BSD-3 license
  • UCSB
    • Help implementation of UCSB double corner
    • Implement variable spacing for smaller GFs
    • 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.
    • add bbp github wiki list of validation events
    • standard/common github continuous integration toos
    • software coverage measurement tools (check with ossian).
    • Define reduced set of tests for BBP verification
    • 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
  • 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
    • Add multi-segment functionality to Irikura Recipe Method 2
  • Validation events
    • Add more Part-A events to BBP Platform Validation (L’Aquila, etc)