Skip to content

Visualization of code in Chapter 5 #121

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

Closed
facusapienza21 opened this issue Apr 10, 2021 · 4 comments · May be fixed by #50
Closed

Visualization of code in Chapter 5 #121

facusapienza21 opened this issue Apr 10, 2021 · 4 comments · May be fixed by #50
Labels
high-priority conceptual error

Comments

@facusapienza21
Copy link

Hi! The html version of chapter 5 about Probabilistic Programming displays the code in such a way that the last line is no visible. I had checked with the other chapters and I just have this problem with chapter 5. I can see the missing lines from the source code.

@pefontana
Copy link
Collaborator

Hi @facusapienza21 !
We know that there is a problem with the html version of chapter 5. We will solve it in the next few days.
By the time, if you want to read the chapter you can download the GitHub repo and open the /05_prob_prog_intro/05_prob_prog_intro.jl file using Pluto.
Thank you!

@pefontana pefontana added the high-priority conceptual error label Apr 12, 2021
@pefontana pefontana linked a pull request Apr 12, 2021 that will close this issue
@facusapienza21
Copy link
Author

Thank you @pefontana , that is exactly what I was doing. Really appreciated all the work you are doing with the book, I am really enjoyingn it!

@unbalancedparentheses
Copy link
Owner

@facusapienza21 thanks for creating the issue. we really appreciate your feedback!

@pefontana
Copy link
Collaborator

We just migrate the book to a bookdown R version!
Now you can see chapter 5 in the html version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high-priority conceptual error
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants