-
Notifications
You must be signed in to change notification settings - Fork 288
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
Code Broken Ch 10 #374
Comments
It doesn't fail per se, because as stated previously to the example: "Let’s again use the Ames housing data to demonstrate these concepts. Section 8.8 summarizes the current state of our Ames analysis." It is using the data resulting from Section 8.8. And when rendering the chapter, it's ensure that this data will be available when calling in the source code:
|
It was just an fyi. I ran the code with the snippets and data file from the repo, indeed with a full clone of the repo. It's not a problem for me but I just thought you might want to know the code in the repo didn't run cleanly. Indeed, for someone just reading and following the book and the instructions it doesn't matter.
Cheers
…On May 16, 2024, 00:29, at 00:29, David ***@***.***> wrote:
It doesn't fail per se, because as stated previously to the example:
"Let’s again use the Ames housing data to demonstrate these concepts.
Section 8.8 summarizes the current state of our Ames analysis."
It is using the data resulting from Section 8.8.
And when rendering the chapter, it's ensure that this data will be
available in the source code when calling
```{r}
source("ames_snippets.R")
load("RData/lm_fit.RData")
```
--
Reply to this email directly or view it on GitHub:
#374 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Thanks, @biscotty666 and @davidrsch! We don't consider this broken code but in fact as designed. Throughout the book, there are summaries at the end of the chapters of where we are in the analysis and then we refer to them in later chapters, like @davidrsch pointed out. There would be too much repeated code otherwise for the reader, in our option. Thanks again! |
I'm so grateful that you provide this for free. It's really top-notch.
Get BlueMail for Android
…On May 16, 2024, 11:39, at 11:39, Julia Silge ***@***.***> wrote:
Thanks, @biscotty666 and @davidrsch! We don't consider this broken code
but in fact as designed. Throughout the book, there are summaries at
the end of the chapters of where we are in the analysis and then we
refer to them in later chapters, like @davidrsch pointed out. There
would be too much repeated code otherwise for the reader, in our
option.
Thanks again!
--
Reply to this email directly or view it on GitHub:
#374 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
In 10.1,
estimate_perf(lm_fit, ames_train)
fails withRunning the code in 8.8 solves the problem.
Thank you for the wonderful book.
The text was updated successfully, but these errors were encountered: