♻️ Refactor DatashaderRasterizer to be up front about datapipe lengths #39
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.
Check during initialization of
DatashaderRasterizerIterDataPipe
on whether the input canvas and vector datapipes have compatible lengths. This is better than finding out that the zip function doesn't work when the datapipe is being iterated over. Added a unit test to cover the 3:2 ratio case and documented why theValueError
is raised on unmatched lengths. Also renamed the previousValueError
on unsupported geometry types toNotImplementedError
to avoid confusion.Motivated by issues discovered in #31 (see af489a8) when some DataPipe functions like https://pytorch.org/data/0.4/generated/torchdata.datapipes.iter.BatchMapper.html do not return any lengths.
Patches #35.