Bug in function power.TOST() [🇷 for BE/BA]

posted by ElMaestro  – Denmark, 2025-08-23 11:46 (311 d 06:01 ago) – Posting: # 24435
Views: 3,513

Hi Hötzi,

❝ Say, you dosed N subjects and are interested in post hoc power of a fraction f of this sample size (e.g., of eligible subjects).


:-D
Accusing me of being a member of the post-hoc power fan club? :-P I think my membership was discontinued around 2007.

For me, pre-study power considerations led me to look into this. Like checking a range of prospective attrition rates to evaluate the actual power.
Before, not after.

I have to say the bug is very minor. I have no relevant real-life (non-simulation) cases where this would make an much meaningful difference - extreme cases with unfavourable combinations of small sample sizes and high variabilities perhaps but most of what I do is not that extreme. A difference of e.g. 0.2% or whatever in a power estimation is to me not of particular relevance since in BE there are various assumption which can be violated and which may have unknown consequences for the magnitude of power.
Dasatinib comes to mind. :crying:

Add to that, that an unfortunate habit in the industry is to adjust assumptions to make the sample size / power meet a target, not the other way around. So, I would not invest too much too much time on fixing this one. PowerTOST is a great tool and the matter here does not in any way detract from its value. You and Detlew and possibly other people involved are doing a great job. Muchas gracias.

Pass or fail!
ElMaestro

Complete thread:

UA Flag
Activity
 Admin contact
23,656 posts in 4,994 threads, 1,571 registered users;
250 visitors (0 registered, 250 guests [including 13 identified bots]).
Forum time: 17:48 CEST (Europe/Vienna)

It requires a very unusual mind
to undertake the analysis of the obvious.    Alfred North Whitehead

The Bioequivalence and Bioavailability Forum is hosted by
BEBAC Ing. Helmut Schütz
HTML5