[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for ch
From: |
Avinoam Kalma |
Subject: |
[Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for chop.m on MS Windows |
Date: |
Sat, 06 Dec 2014 16:41:26 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 |
Follow-up Comment #6, bug #43734 (project octave):
Hi,
I do not think that adding a tolerance here is a good solution.
I would expect that chop(e,3) and 2.72 will have the same
numerical error, so that even though computer 2.72 will
not be the mathematical 2.72, due to limited binary representation,
but chop (e,3)-2.72 should be zero.
But...
>> chop(e,3) - 2.72
ans = 4.4409e-016
Thanks,
Avinoam
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43734>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #43734] Problem in chop.m, Avinoam Kalma, 2014/12/01
- [Octave-bug-tracker] [bug #43734] Problem in chop.m, Avinoam Kalma, 2014/12/01
- [Octave-bug-tracker] [bug #43734] Problem in chop.m, Avinoam Kalma, 2014/12/02
- [Octave-bug-tracker] [bug #43734] Problem in chop.m, Rik, 2014/12/05
- [Octave-bug-tracker] [bug #43734] Problem in chop.m, Avinoam Kalma, 2014/12/06
- [Octave-bug-tracker] [bug #43734] Problem in chop.m, Rik, 2014/12/06
- [Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for chop.m on MS Windows, Rik, 2014/12/06
- [Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for chop.m on MS Windows, Rik, 2014/12/06
- [Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for chop.m on MS Windows,
Avinoam Kalma <=
- [Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for chop.m on MS Windows, Rik, 2014/12/12
- [Octave-bug-tracker] [bug #43734] Tolerance problem in BIST tests for chop.m on MS Windows, Avinoam Kalma, 2014/12/13