Re: lsqlin() error message

[GoSim]

nrjank wrote
> Whether or not to add a noncompatible flag to have octave clip out the
> linearly dependent input as per GoSim's suggestion may warrant further
> discussion.

First make lsqlin give NaN in these cases instead of error. Then if lsqlin
gives NaN try to remove lin. dependent rows and try again.
Like this there is no need to always look for lin. dependent rows. 

Matlab should do this too.

But it could be something else because when two lin. dependent rows were the
only two inputs it worked. 



--
Sent from: http://octave.1599824.n4.nabble.com/Octave-General-f1599825.html