GEOPY-1867: Update inversion docs to describe the auto-mesh option#169
Merged
domfournier merged 6 commits intodevelopfrom Mar 12, 2025
Merged
GEOPY-1867: Update inversion docs to describe the auto-mesh option#169domfournier merged 6 commits intodevelopfrom
domfournier merged 6 commits intodevelopfrom
Conversation
# Conflicts: # docs/inversion/mesh_design.ipynb
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #169 +/- ##
========================================
Coverage 89.60% 89.60%
========================================
Files 81 81
Lines 4598 4598
Branches 606 606
========================================
Hits 4120 4120
Misses 323 323
Partials 155 155 🚀 New features to boost your workflow:
|
domfournier
reviewed
Mar 11, 2025
Collaborator
domfournier
left a comment
There was a problem hiding this comment.
Looks good. See comments.
| "- Modeling resolution (size of the target)\n", | ||
| "\n", | ||
| "Numerical artefacts due to the discretization of topography decay sufficiently when receivers are roughly two cell dimensions away from the nearest edge or corner. Since the lowest drape height from the airborne magnetics is 60 m, a prudent cell size would be in the range of ~30 m. We also want to avoid computing electrical potential differences within the same cell for numerical accuracy. This is condition is guaranteed for cell dimensions less than half the smallest dipole separation - suggesting an even smaller cell (<=20 m) dimension for the 40m dipole direct-current data simulated here.\n", | ||
| "Numerical artefacts due to the discretization of topography decay sufficiently when receivers are roughly two cell dimensions away from the nearest edge or corner of a mesh cell in the air/earth boundary. For example, if the lowest drape height in given airborne survey is 60 m, a prudent cell size would be in the range of ~30 m. Another rule of thumb is that the cell size should be smaller than half the smallest data spacing. This is especially important for electrical methods where the electric field may be discontinuous and numerical artefacts may arise if the cells are not small enough to capture rapid changes in the field. For example, a 40m dipole direct-current survey would suggest a cell size around ~20m.\n", |
Collaborator
There was a problem hiding this comment.
Suggested change
| "Numerical artefacts due to the discretization of topography decay sufficiently when receivers are roughly two cell dimensions away from the nearest edge or corner of a mesh cell in the air/earth boundary. For example, if the lowest drape height in given airborne survey is 60 m, a prudent cell size would be in the range of ~30 m. Another rule of thumb is that the cell size should be smaller than half the smallest data spacing. This is especially important for electrical methods where the electric field may be discontinuous and numerical artefacts may arise if the cells are not small enough to capture rapid changes in the field. For example, a 40m dipole direct-current survey would suggest a cell size around ~20m.\n", | |
| "Numerical artefacts due to the discretization of topography decay substantially when receivers are roughly two cell dimensions away from the nearest edge or corner of a mesh cell in the air/earth boundary. For example, if the lowest drape height in a given airborne survey is 60 m, a prudent cell size would be in the range of ~30 m. Another rule of thumb is that the cell size should be smaller than half the smallest data spacing. This is especially important for electrical methods where the electric field may be discontinuous and numerical artefacts may arise if the cells are not small enough to capture rapid changes in the field. For example, a 40m dipole direct-current survey would suggest a cell size around ~20m.\n", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GEOPY-1867 - Update inversion docs to describe the auto-mesh option