Full refactor#84
Open
Sorrento110 wants to merge 15 commits into
Open
Conversation
Contributor
|
@Sorrento110 you should definitely update the I also think we should consider changing the terminology a bit since now when we talk about normalization we mean two things:
Maybe the latter should just be called |
…ture scaling, ready for intermediate release.
…ion and still getting some issues, but progress being made.
This file contains hidden or 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
2 participants
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.
Files split, docker cleaned up.
Working currently on time normalization cleanup. Using function in new time_processor.py to accomplish this as well as changing functions in normalizer.py to simplify. remove assoc objects and collapse the segregation of primary vs non primary time entries in the date dictionary.
Next step in refactor is to change the geo normalization code to be simplified.
Added 0 to 1 normalization code but it is not used in the normalizer. There is the potential to use this code separately from the regular data normalizer as a "last step" which is still undecided.