octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #38292] binopdf(0, n, 0) gives NaN instead of


From: anonymous
Subject: [Octave-bug-tracker] [bug #38292] binopdf(0, n, 0) gives NaN instead of 1
Date: Sat, 09 Feb 2013 19:31:32 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; (R1 1.6); .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

URL:
  <http://savannah.gnu.org/bugs/?38292>

                 Summary: binopdf(0,n,0) gives NaN instead of 1 
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sat Feb  9 19:31:30 2013
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Arie ten Cate
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

By definition, with n > 0: 
 
   binopdf(0,n,0) == 1 

This is the probability that out of n experiments, each with zero probability
of success, the are zero successes. However, Ocave gives a NaN instead of 1.

With positive but very-near-zero probability of success, Octave gives a 1. For
instance: 
 
   binopdf(0,2,1E-20) == 1 

With a finite machine precision, this is correct. 

   





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38292>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]