Problem with equating for loop index to a variable.
1 Ansicht (letzte 30 Tage)
Ältere Kommentare anzeigen
Jake G
am 13 Mai 2016
Kommentiert: Roger Stafford
am 14 Mai 2016
I run the following code and it does not produce the expected results:
% code
clear all
FlowRate=0.6;
for ThermalImpCurve = 0.2:0.2:1.6
if FlowRate==ThermalImpCurve
ThermalImpCurve
break;
end
end
if the variable FlowRate is 0.6 or 1.4 the loop does not break.
1 Kommentar
Stephen23
am 13 Mai 2016
Welcome to the world of floating point number calculations!. This is such a common topic that the wiki has an explanation of it too:
There are hundreds of threads asking the same question (with the same answer)
and finally:
Akzeptierte Antwort
Roger Stafford
am 13 Mai 2016
You should read Cleve Moler's document on the subject at
http://www.mathworks.com/company/newsletters/news_notes/pdf/Fall96Cleve.pdf
The trouble in this particular example is that binary floating point numbers are incapable of being exactly equal to values such as 0.6 or 1.4, so matlab must approximate these values. As it happens, its approximation for the original ‘FlowRate’ is slightly different from that generated by the colon operator in ThermalImpCurve, hence the failure to recognize your intended equalities. You should not demand exact equality in such situations but allow tiny error tolerances.
2 Kommentare
Roger Stafford
am 14 Mai 2016
To add to the discussion above, here are the two differing binary representations of 0.6 . FlowRate=0.6 in matlab’s binary double is actually represented by:
0.10011001100110011001100110011001100110011001100110011
whereas ThermalImpCurve = 0.2:0.2:1.6 at the third element is represented by:
0.10011001100110011001100110011001100110011001100110100
As you can see, they differ only by 1 in the least bit out of 53 bits. Neither value is exactly 0.6, which would require infinitely many binary digits. FlowRate is rounded down, whereas ThermalImpCurve(3) was rounded up and is a bit farther off the correct value. This latter is probably due to the fact that the 0.2 increment itself in ThermalImpCurve cannot be exactly represented and so there is possibly a cumulative effect.
Weitere Antworten (0)
Siehe auch
Kategorien
Mehr zu Loops and Conditional Statements finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!