Skip to content

Conversation

@castelao
Copy link
Member

@castelao castelao commented Sep 5, 2025

Migrate away from LazyChunk to LazySubset so we avoid assumptions on the chunk's shapes from input features as well as output costs.

Spin off from #96, which was getting too large and covering multiple scopes.

This is a requirement to allow a cost with a chunk shape different than the input features. It also do not impose that input features dataset to have one single chunk grid between all variables.

Help to distinguish between the variable 'cost' and the swap dataset
formerly also called 'cost'.
@castelao castelao self-assigned this Sep 5, 2025
@castelao castelao added enhancement Update to logic or general code improvements p-medium Priority: medium rust labels Sep 5, 2025
Instead of assuming that cost chunk shape is equal to all source
variables' chunks, we now request input features with ArraySubset.
Those will be removed, but for now let's just silence the warning.
It should be considered an error to request a features variable that
doesn't exist or a subset outside the domain.
@castelao castelao merged commit d80a254 into main Sep 6, 2025
21 checks passed
@castelao castelao deleted the lazy_dataset branch September 6, 2025 00:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Update to logic or general code improvements p-medium Priority: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants