earthquake-design-ws issueshttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues2021-07-06T14:35:51Zhttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/465ASCE41-17 : Account for Supplement 1 of ASCE7-162021-07-06T14:35:51ZLuco, NicolasASCE41-17 : Account for Supplement 1 of ASCE7-16For example, see email from Ali Sumer on 12/30/19.For example, see email from Ali Sumer on 12/30/19.ASCE 7-16 Supplement 1Martinez, Eric M.emartinez@usgs.govMartinez, Eric M.emartinez@usgs.govhttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/446Deploy to Prod Systems2019-08-12T21:48:20ZMartinez, Eric M.emartinez@usgs.govDeploy to Prod SystemsDepends on #445
Only complete this issue if the QC from #445 is acceptable.
- Remove a node from Route53 DNS such that it receives no traffic.
- Deploy application to the removed node
- Perform full data load
- Run QC and verify a...Depends on #445
Only complete this issue if the QC from #445 is acceptable.
- Remove a node from Route53 DNS such that it receives no traffic.
- Deploy application to the removed node
- Perform full data load
- Run QC and verify accuracy/functionality
- Return node to Route53 DNS.
Repeat above steps for second production node.0.12.0https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/480NEHRP-20220 : Finalize response metadata relative to documentation2023-08-03T23:36:16ZLuco, NicolasNEHRP-20220 : Finalize response metadata relative to documentationMore specifically:
* update order of response parameters for consistency with documentation
* add "scienceBaseURL"?
* remove "pgadPercentileFactor"?
* rename "sadFloor" as "dllSpectrum"?
* remove "sadPercentileFactor"?
* remove "maxDirFa...More specifically:
* update order of response parameters for consistency with documentation
* add "scienceBaseURL"?
* remove "pgadPercentileFactor"?
* rename "sadFloor" as "dllSpectrum"?
* remove "sadPercentileFactor"?
* remove "maxDirFactor"?Luco, NicolasLuco, Nicolashttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/479ASCE7-22 via NEHRP-2020 : Smooth out “squigglies” in 2-period spectra2022-12-07T15:14:20ZLuco, NicolasASCE7-22 via NEHRP-2020 : Smooth out “squigglies” in 2-period spectraThe USGS web service (but not the "USGS Seismic Design Geodatabase") originally provided the 2-period spectra early in the update cycle for at least comparison purposes, but I'm hearing that continuing to do so might be resulting in them...The USGS web service (but not the "USGS Seismic Design Geodatabase") originally provided the 2-period spectra early in the update cycle for at least comparison purposes, but I'm hearing that continuing to do so might be resulting in them being used for more than was intended and, hence, perhaps the USGS web service (and thereby the ASCE 7 Hazard Tool) should no longer provide the 2-period spectrum?
Alternatively, perhaps the 2-period spectra could be provided at periods corresponding to the rounded spectral acceleration values, with enough precision of the periods to do so? I'd really hesitate to provide more precise spectral accelerations for the 2-period spectra than for the multi-period spectra, the precision of which was decided with the PUC. But I wouldn't mind providing more precise period values.https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/478ASCE7-16 Supplement 3 and ASCE41-17 Supplement 32022-08-19T18:35:03ZMartinez, Eric M.emartinez@usgs.govASCE7-16 Supplement 3 and ASCE41-17 Supplement 3Add the subject reference documents and web services to the available composite endpoints.
**ASCE7-16**
1. Change service name to "asce7-16s3" (but keep a copy of the current service for reproducibility).
2. Change fa and fv such that t...Add the subject reference documents and web services to the available composite endpoints.
**ASCE7-16**
1. Change service name to "asce7-16s3" (but keep a copy of the current service for reproducibility).
2. Change fa and fv such that they match the values from the NEHRP-2015 service.
3. Add new sm1_exception=sm1*1.5 and sd1_exception=sd1*1.5.
4. Change basis for twoPeriodDesignSpectrum and twoPeriodMCErSpectrum to new sd1_exception and sm1_exception, respectively (in addition to unchanged sds and sms).
**ASCE41-17**
1. Same as ASCE7-16 1 above, except "asce41-17s3".
2. Same as ASCE7-16 2 above.
3. Add fa_note and fv_note like in the ASCE7-16 and NEHRP-2015 services (i.e., "See ASCE7-16 Section 11.4.8").
4. Same as ASCE7-16 3 above, except sx1_exception=sx1*1.5.
5. Same as ASCE7-16 4 above, except horizontalSpectrum from sx1_exception.
6. Add QC.Martinez, Eric M.emartinez@usgs.govMartinez, Eric M.emartinez@usgs.govhttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/477TO DO LIST2022-03-28T19:00:41ZLuco, NicolasTO DO LISTHighest to lowest priorities ...
| What | When | Who |
| ------ | ------ | ------ |
| AASHTO-2023 | June 17 | Brandon, Zach, Nico, Jason, Sanaz, Eric |
| Updates to ASCE7-16 and ASCE41-17 | ASAP | HazDev, Nico |
| ASCE41-23 | 2023 | TBD ...Highest to lowest priorities ...
| What | When | Who |
| ------ | ------ | ------ |
| AASHTO-2023 | June 17 | Brandon, Zach, Nico, Jason, Sanaz, Eric |
| Updates to ASCE7-16 and ASCE41-17 | ASAP | HazDev, Nico |
| ASCE41-23 | 2023 | TBD |
| ... | ... | ... |https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/476NEHRP-2020 : create ASCE7-22 alias?2021-07-06T15:10:12ZLuco, NicolasNEHRP-2020 : create ASCE7-22 alias?https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/475NEHRP-2020 : update https://earthquake.usgs.gov/ws/designmaps/nehrp-2020.html2021-07-06T15:08:15ZLuco, NicolasNEHRP-2020 : update https://earthquake.usgs.gov/ws/designmaps/nehrp-2020.htmlLuco, NicolasLuco, Nicolashttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/474NEHRP-2020 : software release2021-07-06T15:01:48ZLuco, NicolasNEHRP-2020 : software releasehttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/473NEHRP-2020 : update https://earthquake.usgs.gov/ws/designmaps/2021-07-06T14:58:55ZLuco, NicolasNEHRP-2020 : update https://earthquake.usgs.gov/ws/designmaps/When ASCE7-22 public comment ends and we publish the NEHRP-2020 and ASCE7-22 web services, ...
* delete "Undergoing public comment"
* consider removing the disclaimer (yellow box), leaving it only in the documentation of each un-releas...When ASCE7-22 public comment ends and we publish the NEHRP-2020 and ASCE7-22 web services, ...
* delete "Undergoing public comment"
* consider removing the disclaimer (yellow box), leaving it only in the documentation of each un-released serviceLuco, NicolasLuco, Nicolashttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/471ASCE7-16: It seems that when siteClass=E and 0.75<ss<1.0, fa=1.3 rather than ...2021-03-15T13:50:40ZLuco, NicolasASCE7-16: It seems that when siteClass=E and 0.75<ss<1.0, fa=1.3 rather than null or ...... an interpolated values between fa=1.3 and fa=1.2. An example is [here](https://earthquake.usgs.gov/ws/designmaps/asce7-16.json?latitude=45.5&longitude=-122.65&riskCategory=I&siteClass=E&title=Portland%20-%20ConUS). However, this migh...... an interpolated values between fa=1.3 and fa=1.2. An example is [here](https://earthquake.usgs.gov/ws/designmaps/asce7-16.json?latitude=45.5&longitude=-122.65&riskCategory=I&siteClass=E&title=Portland%20-%20ConUS). However, this might be the intended behavior for the asce7-16 service, to be updated in an asce7-16s1 ("supplement 1") service. So @james_nautilustracker.com and I can sort this out, @emartinez can you please point us to the code for asce7-16 fa (and fv, fpga)?https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/470ASCE7-16, NEHRP-2015, ASCE41-17: Compare ROUNDED ss or s1 with 1.0 or 0.2, re...2020-05-30T22:15:17ZLuco, NicolasASCE7-16, NEHRP-2015, ASCE41-17: Compare ROUNDED ss or s1 with 1.0 or 0.2, respectivelyAlso for IBC-2018Also for IBC-2018https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/468ASCE41-17: Errors2020-04-28T14:52:02ZLuco, NicolasASCE41-17: Errorshttps://earthquake.usgs.gov/ws/designmaps/asce41-17.json?latitude=25.75&longitude=-80.2&siteClass=A
https://earthquake.usgs.gov/ws/designmaps/asce41-17.json?latitude=71.3&longitude=-156.8&siteClass=Bhttps://earthquake.usgs.gov/ws/designmaps/asce41-17.json?latitude=25.75&longitude=-80.2&siteClass=A
https://earthquake.usgs.gov/ws/designmaps/asce41-17.json?latitude=71.3&longitude=-156.8&siteClass=Bhttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/464Improve Retry Functionality2019-12-05T22:20:52ZMartinez, Eric M.emartinez@usgs.govImprove Retry FunctionalityWhen loading data, there is a built-in retry in case the connection is lost. This is important since the DOI network is unreliable. It appears sometimes the retry itself fails as well. This should be improved to properly retry when the c...When loading data, there is a built-in retry in case the connection is lost. This is important since the DOI network is unreliable. It appears sometimes the retry itself fails as well. This should be improved to properly retry when the connection fails.
Deploy Log Error Stack:
```
Loading deterministic data set
Loading E1998R1_HI0P02_Deterministic region data
.[transferring][pruning]. Completed in 0.957 seconds
Loading E2003R1_PRVI0P01_Deterministic region data
.[transferring][pruning]. Completed in 0.608 seconds
Loading E2007R1_AK0P05_Deterministic region data
..[transferring][pruning]. Completed in 3.425 seconds
Loading E2008R2_COUS0P01_Deterministic region data
.....................................[transferring][pruning]. Completed in 66.1 seconds
Loading E2012R2_AMSAM0P05_Deterministic region data
..[transferring][pruning]. Completed in 0.612 seconds
Loading E2012R1_GNMI0P10_Deterministic region data
..[transferring][pruning]. Completed in 0.406 seconds
Loading E2014R1_COUS0P01_Deterministic region data
.............Caught exception
Error: write EPIPE
at WriteWrap.afterWrite [as oncomplete] (net.js:789:14)
Re-trying...(1 of 1)
/hazdev-project/src/lib/util/url-stream.js:154
_this.push(d);
^
TypeError: Cannot read property 'push' of null
at PassThrough.response.body.on.d (/hazdev-project/src/lib/util/url-stream.js:154:17)
at PassThrough.emit (events.js:198:13)
at addChunk (_stream_readable.js:287:12)
at readableAddChunk (_stream_readable.js:268:11)
at PassThrough.Readable.push (_stream_readable.js:223:10)
at PassThrough.Transform.push (_stream_transform.js:151:32)
at PassThrough.afterTransform (_stream_transform.js:92:10)
at PassThrough._transform (_stream_passthrough.js:42:3)
at PassThrough.Transform._read (_stream_transform.js:190:10)
at PassThrough.Transform._write (_stream_transform.js:178:12)
```https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/455ASCE41 Max Direction Factors2019-10-31T17:50:41ZMartinez, Eric M.emartinez@usgs.govASCE41 Max Direction FactorsDeal with max direction factors more elegantly in ASCE41 calculations for BSE-1E, BSE-2E, and Custom probabilities. Since these data are pulled from UHT curves which have different pre-applied (i.e. do not include) max direction factors,...Deal with max direction factors more elegantly in ASCE41 calculations for BSE-1E, BSE-2E, and Custom probabilities. Since these data are pulled from UHT curves which have different pre-applied (i.e. do not include) max direction factors, these needed to be treated differently here.
Current solution hard-codes appropriate max-direction factors into the code. Prefer a data-driven approach.https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/454In IBC-2015, either change pgadFloor from 0.6 to 0.5, or ...2020-06-04T03:58:14ZLuco, NicolasIn IBC-2015, either change pgadFloor from 0.6 to 0.5, or ...... replace all pga values (of pgauh, pgad, pga, fpga, pgam) with a reference to ASCE 7 (and remove the pga-related metadata), or remove all of the pga-related parameters from the response.... replace all pga values (of pgauh, pgad, pga, fpga, pgam) with a reference to ASCE 7 (and remove the pga-related metadata), or remove all of the pga-related parameters from the response.2019-09-29https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/440NEHRP-2020 : Remove sam.values2021-07-06T14:37:10ZWilson, Christopher Scottcswilson@usgs.govNEHRP-2020 : Remove sam.valuesWilson, Christopher Scottcswilson@usgs.govWilson, Christopher Scottcswilson@usgs.govhttps://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/412NEHRP-2020 : Vertical Spectra2021-07-06T14:52:53ZMartinez, Eric M.emartinez@usgs.govNEHRP-2020 : Vertical SpectraUse vertical coefficient `cv` from #411 to compute the vertical spectra. Logic should be the same as NEHRP 2015. Nico/Sanaz will note any differences.Use vertical coefficient `cv` from #411 to compute the vertical spectra. Logic should be the same as NEHRP 2015. Nico/Sanaz will note any differences.https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/411NEHRP-2020 : Vertical Coefficient2021-07-06T14:52:21ZMartinez, Eric M.emartinez@usgs.govNEHRP-2020 : Vertical CoefficientImplement function to compute vertical component `cv` for NEHRP 2020. Nico/Sanaz will provide the logic for this.Implement function to compute vertical component `cv` for NEHRP 2020. Nico/Sanaz will provide the logic for this.https://code.usgs.gov/ghsc/hazdev/earthquake-design-ws/-/issues/374AASHTO Method Documentation2019-04-01T17:34:23ZMartinez, Eric M.emartinez@usgs.govAASHTO Method DocumentationCorrect documentation for `computeBasicDesign` in the `aashto_2009-factory` class. Notably:
- `data` is an object, not an array
- `metadata` is not used, no need to mention it
- `pga` is also included on the returned promise resolutionCorrect documentation for `computeBasicDesign` in the `aashto_2009-factory` class. Notably:
- `data` is an object, not an array
- `metadata` is not used, no need to mention it
- `pga` is also included on the returned promise resolution