-
Notifications
You must be signed in to change notification settings - Fork 262
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
Add home sale forecast usecase into documentation #1132
Conversation
xzdandy
commented
Sep 16, 2023
•
edited by gaurav274
Loading
edited by gaurav274
- Add home sale forecast use case into documentation
ID 'propertytype' | ||
FREQUENCY 'W'; | ||
|
||
While running this query, EvaDB will train different models respectively for different property types (i.e., house, unit). Here is the query's output ``DataFrame``: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand this sentence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is house
and unit
have very different prices. So we need to train different model for them. The ID column is similar to the GROUP BY. How do you think we should rephrase the sentence?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add this clarification. My confusion was that we are creating a single function but you mention multiple models.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rephrased. Please check if it is easier to understand now.