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

[Nicholas Jankowski]

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

regarding the ability to drop q - it appears that the behavior of LU changes
based on whether or not q is requested as an output?

"When called with two or three output arguments and a sparse input matrix, lu
does not attempt to perform sparsity preserving column permutations. Called
with a fourth output argument, the sparsity preserving column transformation Q
is returned, such that P * A * Q = L * U."

I don't quite understand the internals enough to know if that would be a
problem for subsequent operations.

does calling the function like [~,u,p,~] = lu (eqs, "vector") work, and does
it make a difference?

    _______________________________________________________

Reply to this item at:

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

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