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
756860b7
Commit
756860b7
authored
3 years ago
by
Powers, Peter M.
Browse files
Options
Downloads
Patches
Plain Diff
source types update
parent
b80f0c79
No related branches found
No related tags found
1 merge request
!525
Docs move
Changes
3
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
docs/Magnitude-Frequency-Distributions.md
+27
-0
27 additions, 0 deletions
docs/Magnitude-Frequency-Distributions.md
docs/Model-Files.md
+3
-1
3 additions, 1 deletion
docs/Model-Files.md
docs/Source-Types.md
+214
-511
214 additions, 511 deletions
docs/Source-Types.md
with
244 additions
and
512 deletions
docs/Magnitude-Frequency-Distributions.md
+
27
−
0
View file @
756860b7
...
...
@@ -254,3 +254,30 @@ anywhere in the file heirarchy and may be overridden in nested directories.
Depending on the types of MFDs being modeled, a rate file may contain Gutenberg-Richter a-values
or magnitude-specific rates. The branches of a rate-tree commonly have the generic ID's:
`[R1, R2, R3, ...]`
to support matching rate-trees across source-tree branches.
```
xml
<!-- (optional) A magnitude uncertainty model that will be
applied to every source:
- <Epistemic/> varies mMax and scales variant rates by
the supplied weights; it is only ever applied to SINGLE
and GR MFDs.
- 'cutoff' is magnitude below which uncertainty will be
disabled.
- <Aleatory/> applies a (possibly moment-balanced) ±2σ
Gaussian distribution to mMax; it is only ever applied
to SINGLE MFDs (possibly in conjunction with epistemic).
- 'count' is the number of magnitude bins spanned by
the distribution.
- <Aleatory/> or '<Epistemic/>', or the entire block
may be omitted. -->
<MagUncertainty>
<Epistemic
cutoff=
"6.5"
deltas=
"[-0.2, 0.0, 0.2]"
weights=
"[0.2, 0.6, 0.2]"
/>
<Aleatory
cutoff=
"6.5"
moBalance=
"true"
sigma=
"0.12"
count=
"11"
/>
</MagUncertainty>
<SourceProperties
ruptureScaling=
"NSHM_FAULT_WC94_LENGTH"
/>
</Settings>
```
This diff is collapsed.
Click to expand it.
docs/Model-Files.md
+
3
−
1
View file @
756860b7
...
...
@@ -53,7 +53,9 @@ Depending on context, value can be a number, string, or object. For example:
```
If the
`value`
member is absent, then the branch
`id`
is also the
`value`
. Logic tree weights must
sum to one. Examples of logic trees present in a hazard model are described below.
sum to one. Examples of logic trees present in a hazard model are described below. An
`id`
or
`value`
member value in ALL_CAPS indicates the value is one of a fixed number of options commonly
referred to as an enum.
### Source Model Logic Trees
...
...
This diff is collapsed.
Click to expand it.
docs/Source-Types.md
+
214
−
511
View file @
756860b7
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