Manuscript Error: about bookcode_edition1 HOT 8 CLOSED

also, although probably obvious, to make the code run import matplotlib.pyplot as plt should be added to page xix code as well.

from bookcode_edition1.

also, Code 1.5 on page 9 has an extra trailing parenthesis.

from bookcode_edition1.

hey @aaelony the code is not meant to be runnable if copy and pasted just from the code blocks in the book itself. This is because if we included all the code needed to run every code block throughout the book most of the book would be boilerplate code!

To run the code use the notebooks included, here for example. All these notebooks run end to end with the environment file. Let me know if this makes sense!
https://bayesiancomputationbook.com/notebooks/chp_01.html

Appreciate you opening up these issues, it helps a lot with us understanding how folks are interacting with the text :)

from bookcode_edition1.

also, Code 1.5 on page 9 has an extra trailing parenthesis.

I took a look but couldn't find it, is it this code block?
https://bayesiancomputationbook.com/notebooks/chp_01.html

from bookcode_edition1.

I have the printed edition and am typing the code as I read. I am finding many things that cause runtime errors (all easily fixable). If it isn't helpful to report these issues, I can refrain but it might make the book stronger in the next edition to fix these.

@canyon289, from what you posted above, it looks like the online edition already has fixed the typo in the printed edition.

from bookcode_edition1.

I'll check with the online edition before reporting further issues in the printed edition, should I find any. Thanks for an excellent textbook read so far. :)

from bookcode_edition1.

Its definitely helpful! Our goal is to help you learn the concepts as best as possible, you sharing how youre doing that is very insightful for us. We only have had priors as to how folks would interact with the text, and you're providing the data!

Some acknowledgements and suggestions

1. The printed version has typos (unfortunately), we can't fix them there but we will fix them online!
2. Typing out the code is the best way to retain it so I don't want to discourage you from doing that at all. However note once you get to later chapters that strategy won't work because the code blocks in the book will just show the relevant bits of code, and not importing packages, data loading, etc etc. We figured after seeing the data load once folks would get it, and itd be a bad idea to then show it another 200 times for each example.

• The notebooks though all run end to end. You can find them in the published book site and the repository!

3. If I may ask again please give us feedback! We want to make the second edition 4 times as good as this one, and knowing what is useful for readers helps us out a lot! Feel free to open issue tickets and let us know what you think, and if you mark them as "suggestion" that will help us know what to do with them.

Most of all thank you so much for purchasing and reading the book. We truly appreciate it and I personally hope that you find that the skills and knowledge you gain from this book help you in your own life and work!

from bookcode_edition1.

Great! I'm actually a longtime R user mostly reading the book to see how these same things are done in Python.
Thanks for the responses.

from bookcode_edition1.