Aleutian Arc mfd-trees may be referenced in the wrong rupture-sets (or are inconsistently named)

Unless an mfd-tree (rate and magnitudes) are identical across branches, an mfd-tree ID should probably only be referenced in a single rupture-set. This does not appear to always be the case and needs to be evaluated. All mfd-tree IDs in mfd-map.json and the rupture-sets that reference them are listed in the attached workbook.

For example, pws-geologic-wide-1 is not referenced in any rupture-sets and pws-geologic-narrow-1 is referenced in files:

• segmented/geologic/narrow/1-section/pws/rupture-set.json
• segmented/geologic/wide/1-section/pws/rupture-set.json

The rates of these two MFD trees are the same, but the magnitudes differ.

In other cases (2- and 3-segment rupture branches), the mfd-tree ID does not specify narrow or wide and is used on both branches (magnitudes the same for both widths?). If this is the case, rename the 1-segment branch mfd-tree IDs and get rid of the unused trees.

Aleutians_mfd-tree-id_references.xlsx

mentioned in issue #20 (closed)

changed the description

In the example above, because the multi-section magnitudes for the wide branch become vary large, we use the magnitudes computed for the narrow geometry. As a result, mfd-map names have been refactored to e.g. pws-geologic-1. Progress on this issue was made in !51 (merged) where rates and section definitions were added.

Restructuring the interface logic tree with geodetic and geologic branches only on the 1-section branch should close out this issue.

added 2023 ERF labels

assigned to @pmpowers

mentioned in merge request !58 (merged)

Resolved in !58 (merged)

closed