Repository navigation
Conversation
A sub-network is a directory holding a base network and network sets for part of a wider model. Its sets are referred to by qualified names, such as `upper::options`. Sub-networks are inactive unless a model lists them in `sub_networks` or a network definition names one as its `base`, and selecting from an inactive sub-network is an error. A sub-network's set limits only apply when it is active. Relative data paths in a sub-network's files are rebased onto the project root when they are loaded; output paths are left unchanged. Composing a model now fails if any placeholders are left unresolved, and provenance records the sub-network each component came from. The example project now holds its catchment inflows in a sub-network.
This branch has not been deployed
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.
A sub-network is a directory holding a base network and network sets for part of a wider model. Its sets are referred to by qualified names, such as
upper::options. Sub-networks are inactive unless a model lists them insub_networksor a network definition names one as itsbase, and selecting from an inactive sub-network is an error. A sub-network's set limits only apply when it is active.Relative data paths in a sub-network's files are rebased onto the project root when they are loaded; output paths are left unchanged. Composing a model now fails if any placeholders are left unresolved, and provenance records the sub-network each component came from.
The example project now holds its catchment inflows in a sub-network.