ngoodman
ngoodman
The offending example was redundant anyhow. Removed in ac7f9227be88eea587f8219197db713a0c00f9c1.
Or, eventually, perhaps migrate to [Jekyll](http://jekyllrb.com)?
Note: this is because rejectionSample in probjs is implemented in a way that makes a new trace object for each try, rather than staying within the enclosing trace. It could...
i don’t think anyone went back to work on this / these issues. -N On Mar 28, 2014, at 6:31 PM, Long Ouyang [email protected] wrote: > Noah, what is the...
Or something even more lightweight?
I think a better solution is to have hist and other viz routines (optionally) take a thunk (instead of a list of data points). This thunk is a data stream,...
`iota`, `zip`, `filter` `string-append`, `string-trim` --- more generally [string stuff](http://sicp.ai.mit.edu/Fall-2004/manuals/scheme-7.5.5/doc/scheme_7.html) `save`, `load`, `write` (should happen soon, and be tied to parameter passing for node runscript). `display` (depends on webworker transition?).
it may be helpful to use `observe` instead of `factor` plus `score` (though it does something very similar). you can return the object of all strengths (`{player1: strength('Player-1'), player2: ...})...
i worked around this in ch6 of probmods, by getting rid of `mem`. at some point we should find a solution, though this is a pretty unused corner case....
i have mixed feelings about this. on the one hand, we do need to clean up the confusion about `dist.score(val)` vs `sample(dist)`. introducing `score(dist, val)` is the most straightforward solution....