Feature/chainage indexing #86
Merged
Conversation
This file contains 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
…rating over ResultReach.reaches
|
Added one last change so that gridpoints can also be indexed by number: res = Res1D("my_results.res1d")
res.reaches['river'][0]
# ...returns first ResultGridPoint
res.reaches['river'][-1]
# ...returns last ResultGridPoint |
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.
This PR lets you index chainages of reaches with autocompletion as follows:
It also adds a way to actually test autocompletions with ipykernel.
It introduces one breaking change. Currently ResultReach can be iterated over and indexed numerically into the IRes1DReach objects. This is still possible to do, but now needs to be done on the ResultReach.reaches member.