bugGNU Octave - Bugs: bug #58707, [octave forge] (statistics)...

 
 

bug #58707: [octave forge] (statistics) ttest/ttest2 doc is wrong about hypothesis testing

Submitter:  None
Submitted:  Sun 05 Jul 2020 10:32:39 AM UTC
   
 
Category:  Octave Package Severity:  2 - Minor
Priority:  3 - Low Item Group:  Documentation
Status:  Fixed Assigned to:  None
Originator Name:  Samuel St-Jean Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 5.2.0
Operating System:  * Any Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 26 Jul 2022 09:21:07 PM UTC, comment #4: 

@Markus:
Yeah I know, but several people have had (and maybe still have) those rights with a clause to not use it for the repo, just the trackers.
E.g., these days I rarely if ever push csets to Octave's core repo, but I still do bug & patch triage.
So it's just a choice of the site admin I suppose.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 26 Jul 2022 09:03:49 AM UTC, comment #3: 

@Philip: I don't think it is possible to give admin access to the tracker without also allowing push rights to the repo...

Markus Mützel <mmuetzel>
Group administrator
Mon 25 Jul 2022 06:17:30 PM UTC, comment #2: 

@pr0m1th3as (Andreas)
Can you close bug reports yourself? If not ask the site admins.

I'll close this one for you.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 25 Jul 2022 02:05:01 PM UTC, comment #1: 

I see your point, although your suggestion is also not properly stated. Made changes in the function's texinfo documentation to properly acknowledge what rejecting the null means.
Commit 651e950 at https://github.com/gnu-octave/statistics/commit/651e95026d986eb457f82a459e5185432e2c830a
Closed

Andreas Bertsatos <pr0m1th3as>
Sun 05 Jul 2020 10:32:39 AM UTC, original submission:  

The documentation for both function states that (about lines 44-45)

If @var{h} is 0 the null hypothesis is accepted, if it is 1 the null hypothesis is rejected.

But this is incorrect, the null hypothesis is never accepted. It would be factually correct to instead state

If @var{h} is 1 the null hypothesis is rejected, if is 1 the null hypothesis can not be accepted.

Which has a completely different meaning (we can never accept the null hypothesis). It is possible other stat related function also make that mistake, I did not check all of them out.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by pr0m1th3as (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-07-25 philipnienhuis StatusNone Fixed
        Open/ClosedOpen Closed
    2020-07-09 mtmiller Severity3 - Normal 2 - Minor
        Priority5 - Normal 3 - Low
        Summary[statistics toolbox] ttest/ttest2 doc is wrong about hypothesis testing [octave forge] (statistics) ttest/ttest2 doc is wrong about hypothesis testing

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code