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

Broken link in README #256

Closed
treigerm opened this issue Mar 31, 2021 · 5 comments
Closed

Broken link in README #256

treigerm opened this issue Mar 31, 2021 · 5 comments

Comments

@treigerm
Copy link
Contributor

The link in the second sentence of the parallel sampling sentence points to a webpage which does not seem to exist (https://turing.ml/dev/docs/library/advancedhmc/parallel_sampling). Is this a page that is supposed to be added for the standalone docs?

@xukai92
Copy link
Member

xukai92 commented Apr 9, 2021

That might be updated to https://turing.ml/dev/docs/using-turing/guide#sampling-multiple-chains.
But this link is no longer informative to AHMC users, as many of the patterns have been built into AbstractMCMC now and users doesn't need to write from scratch any more if using Turing directly.

@treigerm
Copy link
Contributor Author

The link is supposed to give information about vectorized sampling as the full sentence says:

It also supports vectorized sampling for static HMC and has been discussed in more detail in the documentation here.

Is the vectorized sampling already available for Turing and does AbstractMCMC have an interface for it?

@xukai92
Copy link
Member

xukai92 commented Apr 16, 2021

Is the vectorized sampling already available for Turing and does AbstractMCMC have an interface for it?

No.

IIRC that part was written by @Vaibhavdixit02.
Can you remind us what was that supposed to link to?

@Vaibhavdixit02
Copy link
Contributor

Yeah that was supposed to get a separate page in the docs, I think my unfinished PR might have the structure of what it was

@yebai yebai closed this as completed Aug 2, 2023
@yebai
Copy link
Member

yebai commented Aug 2, 2023

This is likely fixed now.

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

4 participants