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

[Nicholas Jankowski]

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

I'll step through a single large test and watch the memory at each step.

Right now I'm trying to step through and figure out why the LU method is
getting different triangle volumes than the other methods related to comment
#20.  It think one of the ordering/reordering steps might be off. 

simplex volumes before removal:

old code:

vol =

        0
   0.5000
  -0.5000
        0
  -0.5000
   0.5000
        0
   0.5000
   0.5000
   0.5000
  -0.5000
  -0.5000
  -0.5000
   0.5000
   0.5000

LU code:
Compressed Column Sparse (rows = 1, cols = 15, nnz = 13 [87%])

  (1, 1) -> 1
  (1, 3) -> 0.5000
  (1, 4) -> 1
  (1, 5) -> 0.5000
  (1, 6) -> 1
  (1, 7) -> 0.5000
  (1, 8) -> 0.2500
  (1, 10) -> 0.5000
  (1, 11) -> 1
  (1, 12) -> 0.2500
  (1, 13) -> 0.2500
  (1, 14) -> 0.5000
  (1, 15) -> 1


(2 and 9 missing, so zero.  the fact that we're getting 1s and .25s is what
makes me think it's an ordering issue)



    _______________________________________________________

Reply to this item at:

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

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