47 add option to retain ghost points in nested nemodatatrees - #50
Merged
oj-tooth merged 4 commits intoAug 14, 2026
Merged
Conversation
…g `nbghost_child=None`.
…he size of NEMODataTree domains w & w/o ghost-points.
…ructing NEMODataTrees to docs.
2 tasks
oj-tooth
deleted the
47-add-option-to-retain-ghost-points-in-nested-nemodatatrees
branch
August 14, 2026 15:35
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.
Retain ghost points in nested NEMODataTrees including a hierarchy of domains.
nbghost_child=Noneinfrom_paths()andfrom_datasets()constructors to enable users to optionally bypass clipping ghost points in child domains.processing.pymodule_get_child_indices()function to fill ghost point parent indices with NaN values when located outside of the domain defined in the inputnestsdictionary.nbghost_child=None- ghost points are retained.linsshparameter rename and include discussion on the use ofvcowhen constructing a NEMODataTree.Closes Issue #47