[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values |
Date: |
Thu, 30 Nov 2017 12:07:23 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #32, bug #49523 (project octave):
@Marco: Is it possible to pick the runtime parameters such as the
initialization vector v0 and the maximum number of iterations is such that at
least some of the returned values are NaN? I know you have initialized both
of those items, but I wonder whether we should attempt to optimize those, or
maybe we should relax the tests. For example, this is a failing test
A = toeplitz ([-2, 1, zeros(1, 8)]);
A = kron (A, eye (10)) + kron (eye (10), A);
opts.v0 = (1:100)';
opts.maxit = 3;
warning ("off", "Octave:eigs:UnconvergedEigenvalues", "local");
d = eigs (A, 4, "lm", opts);
assert (d(2:4), [NaN; NaN; NaN]);
!!!!! test failed
ASSERT errors for: assert (d (2:4),[NaN; NaN; NaN])
Location | Observed | Expected | Reason
(1) -7.365 NaN 'NaN' mismatch
What if we relaxed the conditions for the assert so that it was
assert (d(3:4), [NaN; NaN]);
This would still verify that unconverged Ritz values are returned as NaN, but
wouldn't require that exactly 3 Ritz values be unconverged.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49523>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, (continued)
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Dmitri A. Sergatskov, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Rik, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Dmitri A. Sergatskov, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Marco Caliari, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Dmitri A. Sergatskov, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Marco Caliari, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Dmitri A. Sergatskov, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Marco Caliari, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Dmitri A. Sergatskov, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values, Rik, 2017/11/30
- [Octave-bug-tracker] [bug #49523] eigs (R2013b and later) uses NaNs, not zeros, for unconverged Ritz values,
Rik <=