为什么这些双打的返回值是 -1.#IND?

Why are the return values of these doubles -1.#IND?(为什么这些双打的返回值是 -1.#IND?)
本文介绍了为什么这些双打的返回值是 -1.#IND?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有:

double score = cvMatchContourTrees( CT1, CT2, CV_CONTOUR_TREES_MATCH_I1, 0.0 );
        cout<<score<<endl;

有些值返回为 -1.#IND.除此之外,正值是正常的,如 1.34543.

There are values returned as -1.#IND. Other than that, the positive values are normal, like 1.34543.

为什么会这样?我该如何解决?

Why does this happen? How do I solve it?

推荐答案

正如 Frederic 所说,这是 '不是数字' 由 Windows 上的 Visual Studio 构建的应用程序格式化.John D Cook 有一个优秀参考:

As Frederic says, it's the result of a 'Not a Number' being formatted by an application built with visual studio on windows. John D Cook has an excellent reference:

Windows 将 NaN 显示为 -1.#IND(IND"代表不确定"),而 Linux 显示为 nan.

Windows displays a NaN as -1.#IND ("IND" for "indeterminate") while Linux displays nan.

...

简而言之,如果您得到 1.#INF 或 inf,请查找溢出或被零除.如果得到 1.#IND 或 nan,则查找非法操作.

In short, if you get 1.#INF or inf, look for overflow or division by zero. If you get 1.#IND or nan, look for illegal operations.

如果您对字符串进行任何格式化,请注意截断;我在处理这些类型时遇到了相关问题自己的错误.

Watch out for truncations if you do any sort of formatting with your string; I've encountered related issues when handling these sorts of errors myself.

这篇关于为什么这些双打的返回值是 -1.#IND?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Rising edge interrupt triggering multiple times on STM32 Nucleo(在STM32 Nucleo上多次触发上升沿中断)
How to use va_list correctly in a sequence of wrapper functions calls?(如何在一系列包装函数调用中正确使用 va_list?)
OpenGL Perspective Projection Clipping Polygon with Vertex Outside Frustum = Wrong texture mapping?(OpenGL透视投影裁剪多边形,顶点在视锥外=错误的纹理映射?)
How does one properly deserialize a byte array back into an object in C++?(如何正确地将字节数组反序列化回 C++ 中的对象?)
What free tiniest flash file system could you advice for embedded system?(您可以为嵌入式系统推荐什么免费的最小闪存文件系统?)
Volatile member variables vs. volatile object?(易失性成员变量与易失性对象?)