User talk:Hailholyghost: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
Line 9:
[[User:Eoraptor|Eoraptor]] ([[User talk:Eoraptor|talk]]) 11:37, 8 December 2017 (UTC)
:Welch's t-test is easy, the reason I created this page is because I had no idea how to calculate the integration, which is the point of the page. This page is meant to calculate this the same as R's "t.test(x,y,paired=FALSE)" If this page were about the t-test, as you say it is, the C code would have 1 line, and is completely trivial. The point of the page is to show how to do the non-trivial things: integration. I spent weeks figuring out how to do this, and your title change obfuscates my hard work.--[[User:Hailholyghost|Hailholyghost]] ([[User talk:Hailholyghost|talk]]) 12:51, 8 December 2017 (UTC)
::Then this is a very badly designed task. There are already tasks about integration. Anyway, nobody would compute the p-value this way: there are good implementations of special functions, here the incomplete beta function, and usually they make use on specific properties of the functions, like series, continued fraction, optimal rational (Pade like) or polynomial (Chebyshev equioscillation) approximations, etc. If you want the p-value, the "standard" way is to find a special function library. Integration should be a last resort for Rosetta Code, for languages that do not have readily available
::If you want to see how to use a generalist integration routine to compute the p-value, you are doing it wrong. If you want a general task on integration, you are doing it wrong too, and there is already a task about this.
::You write the C code is trivial: really? How? You will need at least the incomplete beta function from [https://www.gnu.org/software/gsl/manual/html_node/Incomplete-Beta-Function.html GSL], and this will require more than one line (you may do more or less what is done here in Fortran or Python). Even getting a working GSL on Windows is not trivial at all.
| |||