Skip to content
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

Date adequate? #6

Open
jackvfb opened this issue Sep 22, 2024 · 0 comments
Open

Date adequate? #6

jackvfb opened this issue Sep 22, 2024 · 0 comments

Comments

@jackvfb
Copy link
Owner

jackvfb commented Sep 22, 2024

Would raw dates work in lieu of a combination of year and julian date?

As the project is currently structured, the raw data is read in with a date field with the format YYY_MM_DD.

When the training set is being prepared, this date is exchanged for two new fields, $year and $jdate which are both ...ints?

Those are then normalized as a step in the model recipe. But what if I skipped the above step, kept the $date field, and normalized that instead? Would recipes know how to handle that? And would that potentially have the advantage of increasing nearest neighbor estimates at boundaries -- helping the algorithm to connect, say December of one year with January of the next year?

@jackvfb jackvfb changed the title Rerun analysis with raw date Date adequate? Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant