You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Map2loop does not slip faults that share the same name and create a loop. This causes the resulting fault surfaces to not work correctly.
In the case below purple should be split into two faults and blue should be split into two faults. It could also be worthwhile merging purple and blue because they create a continuous fault.
Minimal reproducible example
Use Loop sources notebook and look at fault 14655 and 16399
Expected Behavior
map2loop should pick out faults that are not labelled correctly or will create invalid geometries. This could be as simple as looking at the tangent of the line segments of a fault and if the different between two segments is > a threshold the fault is split into two faults.
Actual Behavior
Map2loop does not check the fault geometries
Additional Context
No response
Environment
n/a
Severity
Low
Medium
High
Critical
The text was updated successfully, but these errors were encountered:
Version
3.1.12 0.1.3
Bug Description
Map2loop does not slip faults that share the same name and create a loop. This causes the resulting fault surfaces to not work correctly.
In the case below purple should be split into two faults and blue should be split into two faults. It could also be worthwhile merging purple and blue because they create a continuous fault.
Minimal reproducible example
Use Loop sources notebook and look at fault 14655 and 16399
Expected Behavior
map2loop should pick out faults that are not labelled correctly or will create invalid geometries. This could be as simple as looking at the tangent of the line segments of a fault and if the different between two segments is > a threshold the fault is split into two faults.
Actual Behavior
Map2loop does not check the fault geometries
Additional Context
No response
Environment
n/a
Severity
The text was updated successfully, but these errors were encountered: