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

next manual (2.6.3++) #1420

Closed
bob-carpenter opened this issue Apr 11, 2015 · 10 comments
Closed

next manual (2.6.3++) #1420

bob-carpenter opened this issue Apr 11, 2015 · 10 comments
Assignees
Milestone

Comments

@bob-carpenter
Copy link
Contributor

This is the issue for the next manual release. Please submit all bugs and feature requests for the manual here.

@bob-carpenter bob-carpenter added this to the v2.6.3++ milestone Apr 11, 2015
@randommm
Copy link
Member

Notice: I just created the branch for this issue with some typos fixed.

@syclik
Copy link
Member

syclik commented Apr 23, 2015

From Andrew:

  • We should always lead with the fast code and then explain how it’s equivalent to the non-vectorized version. For example on pp. 61-62 of manual we have multivariate regression with hier model and we start with non-vectorized. This is confusing because if I want to imitate this model myself I have to grab different code snippets.

[Ed. I only created the first optimization. I left the Cholesky one as an add-on.]

@bob-carpenter
Copy link
Contributor Author

Sunil Nandihalli reported on stan-users:

on page 50 of stan-reference-2.6.2.pdf in section 5.7 it is said that C belongs R^(D-1)
should be read as C belongs to R^(K-1)

  • fix it
  • thank Sunil

@bob-carpenter
Copy link
Contributor Author

Andy Choi brought this up on stan-users:

Under the Gaussian Process chapter of the STAN reference manual (Ch 14, version: 2.6.2, pg. 140, 142, 143), the footnote mentioned/suggested the code referenced in the text can be found at: http://mc-stan.org/examples.html

@bob-carpenter
Copy link
Contributor Author

  • add Alp Kucukelbir as a core developer (variational inference!)

@bob-carpenter
Copy link
Contributor Author

From Sebastian Weber:

  • add a reference to

https://software.intel.com/en-us/articles/consistency-of-floating-point-results-using-the-intel-compiler

in your manual concerning the Intel compiler. Most users won’t bother, but I certainly do.

@bob-carpenter
Copy link
Contributor Author

From Heraa Hu in issue #1450

In the manual p. 273 it says: "Stan allows function overloading, where two functions have the same name. For example, an overloaded unit-normal log density function might be declared with an overload of the function unit_normal_log, giving it three signatures with one argument each."

  • remove this and explicitly mention that overloading doesn't work

@jgabry
Copy link
Member

jgabry commented May 28, 2015

On p. 59 (second paragraph of section 5.12) it says

"... and the outcome income, with predictors such as income and age...".

Income is listed both as the outcome and a predictor here. Maybe

  • use education level (or something else) as an example predictor instead of income?

@bob-carpenter
Copy link
Contributor Author

  • add a disclaimer about local optima in mixture models (degenerate solutions where one component collapses into another)

@syclik
Copy link
Member

syclik commented Jun 15, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants