Difference between revisions of "BBP Release Planning"
From SCECpedia
Jump to navigationJump to search| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Feature list for BBP Release v19.1 | + | == Feature list for BBP Release v19.1 == |
| − | |||
| − | |||
* Updated Irikura 1 (multi-segment, 500m GF) | * Updated Irikura 1 (multi-segment, 500m GF) | ||
* Updated GP (multi-segment, 500m GF) | * Updated GP (multi-segment, 500m GF) | ||
| Line 9: | Line 7: | ||
* New Irikura 2 method (single segment, 500m GF) | * New Irikura 2 method (single segment, 500m GF) | ||
* All methods support site response module | * All methods support site response module | ||
| − | * New Validation events, with observations (Parkfield, San Simeon, | + | ** Phased out correction coefficients for Part A validation events |
| + | * New Validation events, with observations (Parkfield, San Simeon, Iwate, Chuetsu-Oki) | ||
| + | * GF for Central California | ||
| + | * Consistent approaches to implementing multi-segment methods. | ||
| + | ** GP and SDSU - multi-seg method 1 (one src file per segment, timing in SRC,timing in SRF file, merge seismograms) | ||
| + | ** SGS, IR1 - multi-seg method 2 (one src file per segment, Rupture generator produces single SRF file, output single set of 3 component seismograms) | ||
| + | * Added script to calculate number of sims needed for convergence | ||
| + | * Added calculation of all 3 components RotD100 and RotD50 | ||
| + | * Migrated batch scripts to use Slurm jobs | ||
| + | |||
| + | == Required for Release == | ||
| + | |||
| + | * Part-A and Part-B validations at 500 m/s and get modeler approval | ||
| + | ** Irikura 1 - pending approval (Feb 4th) | ||
| + | ** Irikura 2 - pending approval (Feb 4th) | ||
| + | ** Song - pending approval (Feb 4th) | ||
| + | ** GP - approved by modeler (Dec 14th) | ||
| + | ** SDSU - under revision (Feb 4th) | ||
| + | ** Exsim - pending reply (Feb 4th) | ||
| + | ** UCSB - waiting 500m/s GF (Feb 4th) | ||
| + | |||
| + | * CSM | ||
| + | ** Remain on the BBP, but disable on user interface | ||
| + | |||
| + | * Update validation event packages | ||
| + | ** Remove amplification factors (Fabio) | ||
| + | ** Revise observations to take care or rotation issues, etc (Christine) | ||
| + | ** Update station list with low and high-pass limits (Christine) | ||
| + | |||
| + | * Irikura 2 | ||
| + | ** Update license and documentation links | ||
| + | |||
| + | * SDSU | ||
| + | ** Code modifications (Kim, Rumi) | ||
| + | |||
| + | * Release evaluation | ||
| + | ** Update super table with new events (Fabio) | ||
| + | |||
| + | == Changes Requiring More Time == | ||
| + | *SDSU multi-segment changes (with updated GP method) | ||
| + | *UCSB multi-segment changes | ||
| + | *Updated Licensing statements in distribution | ||
| + | *Documentation on individual methods | ||
| + | *Migration to Python 3 | ||
| + | *Development of CIG-level user documentation | ||
== Methods with Changes == | == Methods with Changes == | ||
#Graves Pitarka - Multisegment (approved), 500m (approved) | #Graves Pitarka - Multisegment (approved), 500m (approved) | ||
| − | ## Pending - | + | ## Pending - no |
#Olsen - Multisegment (approved), 500m (approved) | #Olsen - Multisegment (approved), 500m (approved) | ||
## Pending Review of method and new codes | ## Pending Review of method and new codes | ||
#Seok Goo Song - Multisegment (approved), 500m (in review) | #Seok Goo Song - Multisegment (approved), 500m (in review) | ||
| − | ## Pending - | + | ## Pending - no |
#Irikura Recipe 1 - Multisegment (under review), 500m GF (approved) | #Irikura Recipe 1 - Multisegment (under review), 500m GF (approved) | ||
## Pending - approval from AP | ## Pending - approval from AP | ||
#Irikura Recipe 2 - Single segment (approved), 500m GF (approved) | #Irikura Recipe 2 - Single segment (approved), 500m GF (approved) | ||
| − | ## Pending - | + | ## Pending - no |
#UCSB - Multisegment (under review), 500m (in review) | #UCSB - Multisegment (under review), 500m (in review) | ||
## Pending - Multi-segment codes | ## Pending - Multi-segment codes | ||
#Exsim - Single segment (approved), Parameter Changes 500m/s (in review) | #Exsim - Single segment (approved), Parameter Changes 500m/s (in review) | ||
## Pending - approval from Karin | ## Pending - approval from Karin | ||
| − | #Anderson - Single | + | #Anderson - Single segment (in review, no 500m/s) |
| − | ## Pending - | + | ## Pending - no |
| + | |||
| + | == Product Backlog == | ||
| + | |||
| + | #Shooting for a code freeze early January, followed by a release. Expected changes/work until then | ||
| + | ##SDSU (Rumi, Kim and Fabio), implementation and testing of main code (perform hybrid merging in time domain instead of frequency domain)post-processors: inter-frequency correlation (almost ready), spatial correlation (may be possible) | ||
| + | ##UCSB (Jorge and Fabio): complete the implementation of multi-fault rupture capability | ||
| + | ##Irikura Method 2 (Hiroe and Fabio): ready, but must include the new disclaimer note in the code (sent to Fabio this week) | ||
| + | ##GP (Rob and Fabio) complete tests for latest RG parameters, requires new Part B criteria for Vs30 = 500 m/s (attached) adjust high-frequency parameters | ||
| + | ##Event files Christine and Fabio) | ||
| + | ##Fabio to use new events files for Part A that include a Tmin limit (we only used Tmax in the past); some records need to be re-processed too. Christine to give all needed file to Fabio soon. | ||
| + | #Christine generated new Part B criteria (low, mean, high) for Vs30=500 m/s, to be used with the new vmods (attached) | ||
| + | #We agreed to not publish amplification factors with the event file anymore and people can either use the site effects module or have simulations at the vmod-specific Vs30. | ||
| + | #We started to discuss the pros and cons of providing both sets of vmods (Vs30 of 863 and 500 m/s). Discussion to be continued. | ||
| + | |||
| + | == Related Entries == | ||
| + | [[BBP]] | ||
Latest revision as of 19:09, 5 February 2019
Contents
Feature list for BBP Release v19.1
- Updated Irikura 1 (multi-segment, 500m GF)
- Updated GP (multi-segment, 500m GF)
- Updated Olsen (multi-segment, 500m GF)
- Update Seok Goo Song (multi-segment, 500m GF)
- Updated Exsim (500m GF)
- New Irikura 2 method (single segment, 500m GF)
- All methods support site response module
- Phased out correction coefficients for Part A validation events
- New Validation events, with observations (Parkfield, San Simeon, Iwate, Chuetsu-Oki)
- GF for Central California
- Consistent approaches to implementing multi-segment methods.
- GP and SDSU - multi-seg method 1 (one src file per segment, timing in SRC,timing in SRF file, merge seismograms)
- SGS, IR1 - multi-seg method 2 (one src file per segment, Rupture generator produces single SRF file, output single set of 3 component seismograms)
- Added script to calculate number of sims needed for convergence
- Added calculation of all 3 components RotD100 and RotD50
- Migrated batch scripts to use Slurm jobs
Required for Release
- Part-A and Part-B validations at 500 m/s and get modeler approval
- Irikura 1 - pending approval (Feb 4th)
- Irikura 2 - pending approval (Feb 4th)
- Song - pending approval (Feb 4th)
- GP - approved by modeler (Dec 14th)
- SDSU - under revision (Feb 4th)
- Exsim - pending reply (Feb 4th)
- UCSB - waiting 500m/s GF (Feb 4th)
- CSM
- Remain on the BBP, but disable on user interface
- Update validation event packages
- Remove amplification factors (Fabio)
- Revise observations to take care or rotation issues, etc (Christine)
- Update station list with low and high-pass limits (Christine)
- Irikura 2
- Update license and documentation links
- SDSU
- Code modifications (Kim, Rumi)
- Release evaluation
- Update super table with new events (Fabio)
Changes Requiring More Time
- SDSU multi-segment changes (with updated GP method)
- UCSB multi-segment changes
- Updated Licensing statements in distribution
- Documentation on individual methods
- Migration to Python 3
- Development of CIG-level user documentation
Methods with Changes
- Graves Pitarka - Multisegment (approved), 500m (approved)
- Pending - no
- Olsen - Multisegment (approved), 500m (approved)
- Pending Review of method and new codes
- Seok Goo Song - Multisegment (approved), 500m (in review)
- Pending - no
- Irikura Recipe 1 - Multisegment (under review), 500m GF (approved)
- Pending - approval from AP
- Irikura Recipe 2 - Single segment (approved), 500m GF (approved)
- Pending - no
- UCSB - Multisegment (under review), 500m (in review)
- Pending - Multi-segment codes
- Exsim - Single segment (approved), Parameter Changes 500m/s (in review)
- Pending - approval from Karin
- Anderson - Single segment (in review, no 500m/s)
- Pending - no
Product Backlog
- Shooting for a code freeze early January, followed by a release. Expected changes/work until then
- SDSU (Rumi, Kim and Fabio), implementation and testing of main code (perform hybrid merging in time domain instead of frequency domain)post-processors: inter-frequency correlation (almost ready), spatial correlation (may be possible)
- UCSB (Jorge and Fabio): complete the implementation of multi-fault rupture capability
- Irikura Method 2 (Hiroe and Fabio): ready, but must include the new disclaimer note in the code (sent to Fabio this week)
- GP (Rob and Fabio) complete tests for latest RG parameters, requires new Part B criteria for Vs30 = 500 m/s (attached) adjust high-frequency parameters
- Event files Christine and Fabio)
- Fabio to use new events files for Part A that include a Tmin limit (we only used Tmax in the past); some records need to be re-processed too. Christine to give all needed file to Fabio soon.
- Christine generated new Part B criteria (low, mean, high) for Vs30=500 m/s, to be used with the new vmods (attached)
- We agreed to not publish amplification factors with the event file anymore and people can either use the site effects module or have simulations at the vmod-specific Vs30.
- We started to discuss the pros and cons of providing both sets of vmods (Vs30 of 863 and 500 m/s). Discussion to be continued.
