[Octave-bug-tracker] [bug #60818] delaunayn - 2D code path vectorization doesn't match nD algorithm

[Nicholas Jankowski]

Follow-up Comment #33, bug #60818 (project octave):

Sorry, sloppy patch again.  playing with this one so much, guess should have
made a got for it.

 Yes, as written it should say 


if (any(nd == [3 4]))


for the currently  written 2d and 3d code paths. (I had removed the 4 for
timing the LU path for 3D).  

I hadn't yet added the higher dimension expansions to this version, but if we
do then higher nd's would go in as well)

q was used up until the last patch which fixed the ordering issue. 

In the last patch I had changed 
[l,u,p,q] to [~,u,p,q]

Can so that with q now too.

This removed the storage requirement for L, but i think this doesn't stop
Octave from building L during the LU, it just discards it, correct? So I don't
think it'll actually make much difference in speed or memory?  

    _______________________________________________________

Reply to this item at:

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

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