-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't require consecutive Node IDs #885
Conversation
@@ -248,7 +248,7 @@ function create_callbacks( | |||
save_subgrid_level, | |||
saved_subgrid_level; | |||
saveat, | |||
save_start = false, | |||
save_start = true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Huite I'm now saving initial subgrid levels as well, just like the regular basin.arrow. I assume you copied this from flow, which is undefined at t0 so we don't save it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this sounds fine.
# TODO The original subgrid IDs are lost and mapped to 1, 2, 3 | ||
@test subgrid.subgrid_id[1:3] == [11, 22, 33] broken = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Huite I assume you want to keep the original subgrid IDs right? If so let's create an issue to fix this. We'd have to store them in the struct Subgrid
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think we should keep them around. Are you opening an issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I opened #895
Fixes #694
It basically was already fixed in the metagraphs refactor, I just had to remove the validation check from Python.
This also adds support for 0, but not negative IDs, as I feel those could be confusing.
I used the trivial model to add some ID variations, and directly added some tests of the Arrow file results that we didn't really have yet.