Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

- JMP User Community
- :
- Discussions
- :
- TOST Equivalence Test error

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

Highlighted
##

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Email to a Friend
- Report Inappropriate Content

TOST Equivalence Test error

Jul 16, 2020 9:00 AM
(302 views)

I followed the Equivalence Test (TOST) example but the output is different from the website.

Website:

>= 6 p=0.0124

<= -6 p<.0001

My output:

<= 6 p=0.0124

>= -6 p<.0001

Essentially, the null hypotheses have been reversed so that rejecting corresponds to non-equivalence. The hypothesis on website appear accurate as rejecting the null indicates evidence that data is within the equivalence region. Why is my software reversing the hypothesis?

I am using JMP 13.2.0

3 REPLIES 3

Highlighted
##

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Email to a Friend
- Report Inappropriate Content

Re: TOST Equivalence Test error

Created:
Jul 16, 2020 9:46 AM
| Last Modified: Jul 16, 2020 10:00 AM
(298 views)
| Posted in reply to message from tkutch 07-16-2020

JMP uses alphabetic or numeric order by default except for a few special cases. Gender is not one of them. So the default order is F is first and M is second. That leads to the results shown in the on-line documentation.

This order is important. JMP will subtract the response of the second level from the response of the first level, so the mean height of sex = F from the mean height of sex = M.

If the order of the sex levels is reversed, then so is the difference (negated). I was able to reproduce your result by adding the Value Order column property and making M first and F second. Is that what you have for the order?

Learn it once, use it forever!

Highlighted
##

@markbailey I have F first and M second in the Value Order column property. I tried switching the order (M first, F second) and yes the mean difference flipped, but the null hypothesis are still <=6 and >= -6.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Email to a Friend
- Report Inappropriate Content

Re: TOST Equivalence Test error

Highlighted
##

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Email to a Friend
- Report Inappropriate Content

Re: TOST Equivalence Test error

I see. I cannot remember if the labelling of the null hypotheses was an issue in JMP 13. You should report this behavior to JMP Technical Support (support@jmp.com). Please report here what you learn from them.

Learn it once, use it forever!