[Top][All Lists]

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

[Octave-bug-tracker] [bug #36732] interp1 does not check input for monot

From: Ben Abbott
Subject: [Octave-bug-tracker] [bug #36732] interp1 does not check input for monotonicity
Date: Mon, 20 Aug 2012 12:23:02 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.25 (KHTML, like Gecko) Version/6.0 Safari/536.25

Follow-up Comment #39, bug #36732 (project octave):

I had inferred the "increasing" / "decreasing" values referred to the "xi"
values (i.e. interp1 (x, y, xi)).

Francesco's thought that they referred to the "x" values prior to the sorting
makes more sense.

We'll need another changeset to fix the manual, correct?

The "distinct" language troubles me since Octave has a "unique()" function. 
The use of "distinct" infers to me that it means something different than
"unique".  Is there a reason why "distinct" is being used as opposed to


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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