https://sami.boo/jaynes/confidence-intervals-vs-bayesian-int... (+ Cauchy example below)
It’s like with test accuracy. Test accuracy is the pre-test probability that the test will give a correct result. But once you have a positive or negative result, which way it turned out plays a part in computing the predictive value. Likewise, once you have computed the interval, the specific bounds you ended up getting can affect the plausibility that they contain the true value.
The conclusion they come to is "it is possible to do better in the individual case by taking into account evidence from the sample that the confidence interval method throws away". That means the confidence interval is inefficient, not incorrect.
But once you have picked one, and you know its bounds (say, [12.1471, 13.8264]), then it’s fallacious to make the post-data reasoning that “because it was picked at random from the set of 90% confidence intervals, it has a 90% chance of containing the true parameter”.
Again, it’s like with medical tests. If a test has 90% sensitivity and 90% specificity, it has 90% accuracy (it will, in 90% of cases, produce a result that matches disease status) – a pre-data statement on the test result (/ on the confidence interval that we will compute). But it does not follow that, if you screen an asymptomatic patient with low prior probability of disease and get a positive result, they have a 90% chance of having the disease – a post-data statement on disease status, given the test result (/ on where the parameter lies, given the interval).
> The conclusion they come to is "it is possible to do better in the individual case by taking into account evidence from the sample that the confidence interval method throws away". That means the confidence interval is inefficient, not incorrect.
It means you know in the individual case that the specific confidence interval does not in fact have a 90% chance of containing the parameter.
The examples that actually ruin the number so far have been asymmetrical. Is there a way to do it with a gaussian? Especially if you're trying to make a reasonable internal?
Sorry, I don’t follow. Let’s say I want to compute a 50% confidence interval for the unknown mean of a Gaussian distribution. I sample two numbers from the distribution, get 9 and 7, compute the interval according to the trivial procedure and get (-∞, ∞). Does the interval (-∞, ∞) have a 50% probability of containing the mean of that Gaussian distribution? I would think it’s closer to 100%.
If what you are saying is “it’s meaningless to talk about the probability of that specific interval containing the unknown-but-fixed parameter” then that’s the purely frequentist view and then you also agree that it’s meaningless to say that [-2.31, 10.31] has a 90% chance of containing the location parameter of the Cauchy distribution that happened to yield the samples 3 and 5. Incidentally, what asymmetry are you referring to in the Cauchy example?
> then that’s the purely frequentist view and then you also agree that it’s meaningless
I'm saying that when you hit "meaningless" you can back up a step to where you actually had randomness and look at that distribution, which gets rid of a lot of these issues.
But after looking at these examples I think it only makes sense in limited circumstances to do that. Like in the trivial example: your final distribution isn't based on the probability of the mean being any particular number. The only probability was back a step and that was 50%.
At this point I still don't think it's objectively wrong to say a particular interval above is 95% likely, but there's too many ways to interpret the statement so nobody should say it is.
The way we're calculating that these intervals are "wrong" is by looking at all the possible parameters that could have given us the samples we got, and checking how often the range contains the parameter. That's a useful calculation but is it the one people expect? I think that depends on the situation. Treating the parameter as being the thing we sample over is misleading, but treating it as fixed is also misleading.