search for: 2346669

Displaying 4 results from an estimated 4 matches for "2346669".

2017 Aug 25
2
Are r2dtable and C_r2dtable behaving correctly?
...help(r2dtable) - Patefield, W. M. (1981) Algorithm AS159. An efficient method of generating r x c tables with given row and column totals. _Applied Statistics_ *30*, 91-97. For those with JSTOR access (typically via your University), available at http://www.jstor.org/stable/2346669 When I start reading it, indeed the algorithm seems start from the expected value of a cell entry and then "explore from there"... and I do wonder if there is not a flaw somewhere in the algorithm: I've now found that a bit more than a year ago, 'paljenczy' found on SO htt...
2017 Aug 25
0
Are r2dtable and C_r2dtable behaving correctly?
...help(r2dtable) - Patefield, W. M. (1981) Algorithm AS159. An efficient method of generating r x c tables with given row and column totals. _Applied Statistics_ *30*, 91-97. For those with JSTOR access (typically via your University), available at http://www.jstor.org/stable/2346669 When I start reading it, indeed the algorithm seems start from the expected value of a cell entry and then "explore from there"... and I do wonder if there is not a flaw somewhere in the algorithm: I've now found that a bit more than a year ago, 'paljenczy' found on SO htt...
2017 Aug 24
3
Are r2dtable and C_r2dtable behaving correctly?
Hello, While doing some enrichment tests using chisq.test() with simulated p-values, I noticed some strange behaviour. The computed p-value was extremely small, so I decided to dig a little deeper and debug chisq.test(). I noticed then that the simulated statistics returned by the following call tmp <- .Call(C_chisq_sim, sr, sc, B, E) were all the same, very small numbers. This, at first,
2017 Aug 25
0
Are r2dtable and C_r2dtable behaving correctly?
...Patefield, W. M. (1981) Algorithm AS159. An efficient method of > generating r x c tables with given row and column totals. > _Applied Statistics_ *30*, 91-97. > > For those with JSTOR access (typically via your University), > available at http://www.jstor.org/stable/2346669 > > When I start reading it, indeed the algorithm seems start from the > expected value of a cell entry and then "explore from there"... > and I do wonder if there is not a flaw somewhere in the > algorithm: > > I've now found that a bit more than a year ago, ...