Handle duplicate timeseries index #3243
Merged
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
TimeSeries
can be created with duplicate time index value.What is the new behavior (if this is a feature change)?
Skipped row when duplicate time index is found during CSV
timeseries
parsingThrows exception in
IrregularTimeSeriesIndex
if the times array contains duplicate or is unorderedDoes this PR introduce a breaking change or deprecate an API?
Other information:
Linked to a practical case in powsybl-dynawo PR 413