For a really good introduction to this topic I recommend of Josh Tenenbaum's Growing a Mind talks, http://videolectures.net/aaai2012_tenenbaum_grow_mind/
I never realized this article would be read by regular folks and am incredibly confused why something I wrote 6 months ago is suddenly all over the internet now.
I'd really like to subscribe to your blog/site so I can read your more substantial set of writings as they appear -- but I can't seem to find the appropriate RSS or ATOM feed on your site. Am I missing something?
<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="http://zinkov.com/rss.xml" />
Any decent RSS reader (e.g. Google Reader, TTRSS) would then detect the feed if the user tried to subscribe to your homepage. Some browsers and browser extensions also provide a one-click subscribe button based on that tag.It's also common to just put a visible link somewhere on the page, since not everyone knows about auto-discovery.
The usual practice seems to be to put a link to the rss feed (the one you just gave) somewhere on the archive page or at the top of each post page.
Thanks again.
Coincidentally, a colleague at lunch yesterday made exactly this observation about Stan, a probabilistic programming language he is using (http://mc-stan.org/).
Stan's notation is very similar to, if not the same as, that shown here. In Stan, those model{} statements are combined with data{} and parameter{} statements that plug in values of interest. The algorithmic details appear to get specified by the command-line invocation.
I found the Stan user guide a bit more enlightening than this essay. The essay shows a bunch of models, but it has very little discussion about what the models mean, or how they express the ideas alluded to in the short introductory paragraphs. The Stan UG does a marginally better job of showing why the model looks the way it does, and relating it to the math they're trying to solve. Still, like this essay, the exposition is definitely pitched toward somebody who already knows the field (unfortunately, not me).