apply config frequency to dataframe #60
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi @holukas
We had an issue where the inferred time frequency list
freq_listinDetectFrequencyhas a length of exactly 2 (["30min", "30T"]). In that case, the if statement fails, but there is no else and theinferred_freqofTimestampSanitizerwill result to beNone.This small adjustment fixes this since the
DetectFrequencyconstructor will never be called because the frequency is already defined on the dataframe index. However, you may want to consider refactor theDetectFrequency-class instead. I leave this design choice up to you. :)