Possible Excel bug? [Software]
Hi ElMaestro,
I guess that I shouldn't be surprised given its history...
Good idea.
In fact, I just checked that
Nice work, M$.
❝ I do not have Excel, but it sounds like an embarrassing implementation.
I guess that I shouldn't be surprised given its history...
❝ Can you try, just for the fun of it, to ask Excel what it thinks the critical value at df=10.1 is for:
❝
❝ a. p=0.9994425014527133
❝ b. p=0.999428447456598
Good idea.
T.INV(0.999442501452713, 10.1) = 4.51612251417097
T.INV(0.999428447456598, 10.1) = 4.50000000000000
In fact, I just checked that
T.DIST(4.5, df, TRUE)
will give exactly the same result for df = 10.1, 10.2, ... 10.9, (increase df but let df < 11). The result only changed when df = 11! Nice work, M$.
—
All the best,
Shuanghe
All the best,
Shuanghe
Complete thread:
- Possible Excel bug? Shuanghe 2019-12-17 13:01 [Software]
- Possible Excel bug? ElMaestro 2019-12-17 13:49
- Possible Excel bug?Shuanghe 2019-12-17 14:15
- Possible Excel bug? mittyri 2019-12-17 14:23
- M$: It’s not a bug, it’s a feature! Helmut 2019-12-17 15:00
- M$: It’s not a bug, it’s a feature! Shuanghe 2019-12-17 15:41
- M$: It’s not a bug, it’s a feature! Helmut 2019-12-17 16:00
- M$: It’s not a bug, it’s a feature! Shuanghe 2019-12-17 15:41
- M$: It’s not a bug, it’s a feature! Helmut 2019-12-17 15:00
- Possible Excel bug? ElMaestro 2019-12-17 13:49