Broadband Sprints

From SCECpedia
Jump to navigationJump to search

Development targets, Trac Tickets, and other activities related to Broadband Platform development

Spring 4

  • Spring Dates - 13 August - 24 August
  1. Add "hard stop" method to bbp_utils
  2. Add arias duration into validation pipeline
  3. Add rotd50 into validation pipeline
  4. Add observation data processing into validation pipeline
  5. End-to-end validation pipeline with both obs and sim processing.
  6. Data products list generated for validation runs.
  7. Make site response processing optional for validation runs
  8. Configure UCSB and SDSU methods to run LOMAP
  9. Post bias plots for LOMAP for 3 main methods on server and on cluster
  10. Update Documentation including Installation and User Guide
  11. Broadband 12.8.0 Release
    1. Full validation tests for three main methods run on both server and cluster.
    2. Produce validation and velocity model packages

Sprint 3

  • Sprint Dates: 30 July - 10 August
  1. Routine plotting of LOMAP full validation with comparison acceleration plots (with fixed label), and Bias GOF plots for LOMA Prieta
  2. LOMAP workflow changed to include rupture generator
  3. Wiki site updated to contain current input files, current GOF, and example comparison plots
  4. URS modules renamed to GP
  5. Documentation on how to setup new GF and validation data
  6. DB code and PEER formatter included in trunk
  7. Rupture generator parameters separated into user selectable (), and modeler adjustable (DLEN, DWID, DT)
  8. ROTD50 running with acceptance test and producing file as part of LOMAP
  9. ARIAS running with acceptance test and producing file as part of LOMAP
  10. Integrate new bbtoolbox into platform

Sprint 2

  • Sprint Dates: 16 July - 27 July
  1. Change validation processing so users specify a velocity model, which then determines the GF used in processing, removing "region" based GF selection in bbp v11.2.3.

Sprint 1

  • Sprint Dates: 2 July - 13 July
  1. Separate Validation Data from BBP software distribution so observational data sets are not distributed as part of BBP software