Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
N
nshmp-haz
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ghsc
National Seismic Hazard Model Project
nshmp-haz
Commits
ba522893
Commit
ba522893
authored
3 years ago
by
Powers, Peter M.
Browse files
Options
Downloads
Plain Diff
Merge branch 'review-doc_typos' into 'main'
Review doc typos Closes
#479
See merge request
!559
parents
4bcf94b2
30ab9798
No related branches found
No related tags found
2 merge requests
!577
Production Release | nshmp-haz
,
!559
Review doc typos
Pipeline
#79757
canceled
3 years ago
Stage: init
Stage: build
Stage: trigger
Changes
3
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
docs/pages/About-the-NSHMP.md
+1
-1
1 addition, 1 deletion
docs/pages/About-the-NSHMP.md
docs/pages/Model-Editions.md
+1
-1
1 addition, 1 deletion
docs/pages/Model-Editions.md
docs/pages/Source-Types.md
+4
-4
4 additions, 4 deletions
docs/pages/Source-Types.md
with
6 additions
and
6 deletions
docs/pages/About-the-NSHMP.md
+
1
−
1
View file @
ba522893
...
...
@@ -11,7 +11,7 @@ Earthquake Hazards Reduction Act of 1977, as amended:
>lifelines, including additional maps needed for performance-based design approaches."
The NSHMP primarily produces long-term NSHMs that are used in U.S. building codes and numerous
other seismic design requirements. The models are used i
s
site-specific analyses and also for
other seismic design requirements. The models are used i
n
site-specific analyses and also for
defining likely earthquake scenarios for emergency planning. NSHMs are considered reference
(or baseline) models used by the risk, insurance and reinsurance industries, and they are also
considered in other industries such as real estate lending. A 9-member steering committee of
...
...
This diff is collapsed.
Click to expand it.
docs/pages/Model-Editions.md
+
1
−
1
View file @
ba522893
...
...
@@ -51,7 +51,7 @@ Puerto Rico & <br/> U.S. Virgin Islands | 2003 | v1.0.0 | | | |
included data to support updates to the U.S. Building Code, specifically hazard curves for peak
ground acceleration (PGA), and 0.2 and 1.0 second spectral accelerations, all at a BC boundary site
class with Vs30 = 760 m/s. Some time later, the model was deployed to the Unified Hazard Tool
(UHT) and included support in the Wester U.S. for calculations at sites other than Vs30 = 760 m/s,
(UHT) and included support in the Wester
n
U.S. for calculations at sites other than Vs30 = 760 m/s,
consistent with dynamic calculations using the 2008 model. Subsequently, we updated the 2014
model with
[
addional periods and site classes
](
https://pubs.er.usgs.gov/publication/ofr20181111
)
.
Doing so required dropping several ground motion models (GMMs) and a redistribution of logic-tree
...
...
This diff is collapsed.
Click to expand it.
docs/pages/Source-Types.md
+
4
−
4
View file @
ba522893
...
...
@@ -40,7 +40,7 @@ spatial PDFs, [below](#spatial-pdfs)). When realizing each source the spatial PD
by each regional rate in a rate-tree.
Grid sources are represented in a model using a logic tree with a
`rupture-sets.json`
defining the
ruptures on each branch. Because gridded seismicity models may be govered by regionally
ruptures on each branch. Because gridded seismicity models may be gover
n
ed by regionally
varying MFD properties (e.g.
`mMax`
), rupture sets for grids are defined in a JSON array.
**rupture-sets.json**
: Defines an array of one or more rupture sets. Multiple rupture sets are
...
...
@@ -175,12 +175,12 @@ Finite fault source representation. The geometry, properties and rupture MFDs of
are defined by one or more GeoJSONs and associated configuration. Depending on the complexity of
the source, it may be represented using a single GeoJSON or result from stitching together
multiple GeoJSONs (see note on fault section stitching,
[
below
](
#fault-section-stitching
)
). If a
fault source is represented with a logic tree
k
then
`rupture-set.json`
defines the ruptures for
fault source is represented with a logic tree then
`rupture-set.json`
defines the ruptures for
each branch. Depending on the MFDs and scaling relations used to determine a rupture size, some
ruptures may fill the entire source model while smaller events are modeled as 'floating' ruptures;
they occur in multiple locations on the fault surface with appropriately scaled rates. MFDs
associated with finite fault models may be explicit
e
ly defined or
or
derived from slip rates.
Fault rupture rates may be modeled using explicit
e
ly defined MFDs or logic trees of slip rate.
associated with finite fault models may be explicitly defined or derived from slip rates.
Fault rupture rates may be modeled using explicitly defined MFDs or logic trees of slip rate.
**fault-source.geojson**
: Defines the geometry and properties of a single source. In the example
below the presence of a
`rate-map`
property indicates MFDs should be constructed from the supplied
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment