-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The data parsing step adds spurious values #2
Comments
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jul 27, 2022
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jul 30, 2022
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jul 30, 2022
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 2, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 3, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 4, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 5, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 5, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 5, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 5, 2023
paulbroek
added a commit
to paulbroek/GoodreadsScraper
that referenced
this issue
Jan 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the
dateutil.parse
function cannot find a component of the timestamp (any of day, month or year), it replaces it with the current date's components.This can cause problems in later steps of the analysis, where spurious patterns in time series will show up. This can be fixed either by:
The text was updated successfully, but these errors were encountered: