[BUG] Fix TimeSeries
data does not match length of timestamps should raise an error when created
#1538
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.
Motivation
This is a follow up on the issue described in #1536 to prevent a
TimeSeries
being created with timestamps that does not match the length of data.This PR changes
TimeSeries
_check_time_series_dimension
check to warn when reading from file and raise an error when constructing new data.This change also affects
ImageSeries
check that will also raise a ValueError when anImageSeries
is being created with timestamps that do not match the length of data. IfImageSeries
is used with external file, then this error or warning will not be triggered.Resolve #1536
How to test the behavior?
Checklist
flake8
from the source directory.