[Octave-bug-tracker] [bug #63376] tsearchn quite slow (compared to tsearch)

[Rik]

Update of bug #63376 (project octave):

                  Status:          Ready For Test => In Progress            

    _______________________________________________________

Follow-up Comment #9:

I checked in an additional changeset to use more Octave coding conventions in
tsearchn.m.  See http://hg.savannah.gnu.org/hgweb/octave/rev/c664627d601e.

One of the things I noticed was this line:


    inside = all (b >= -1e-12, 2);  # -1e-12 instead of 0 for rounding errors


Is the hard criteria of -1e-12 appropriate or should it scale in some way with
the input?  Also, is it ever possible that the input are not double values,
but single values, and this cut-off should change to reflect that?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63376>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/