将双精度舍入为 x 有效数字
如果我有一个 double (234.004223) 等,我想在 C# 中将其四舍五入到 x 个有效数字。
到目前为止,我只能找到四舍五入到小数点后 x 位的方法,但是如果数字中有任何 0,这只会删除精度。
例如,0.086 到小数点后一位变成 0.1,但我希望它保持在 0.08。
If I have a double (234.004223), etc., I would like to round this to x significant digits in C#.
So far I can only find ways to round to x decimal places, but this simply removes the precision if there are any 0s in the number.
For example, 0.086 to one decimal place becomes 0.1, but I would like it to stay at 0.08.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(17)
该框架没有内置函数来舍入(或截断,如您的示例中)为多个有效数字。 不过,实现此目的的一种方法是缩放数字,使第一个有效数字位于小数点之后,四舍五入(或截断),然后缩小。 下面的代码应该可以解决这个问题:
如果,如您的示例所示,您确实想要截断,那么您需要:
The framework doesn't have a built-in function to round (or truncate, as in your example) to a number of significant digits. One way you can do this, though, is to scale your number so that your first significant digit is right after the decimal point, round (or truncate), then scale back. The following code should do the trick:
If, as in your example, you really want to truncate, then you want:
我已经使用 pDaddy 的 sigfig 函数几个月了,发现其中有一个错误。 不能取负数的 Log,因此如果 d 为负数,则结果为 NaN。
以下更正了该错误:
I've been using pDaddy's sigfig function for a few months and found a bug in it. You cannot take the Log of a negative number, so if d is negative the results is NaN.
The following corrects the bug:
在我看来,您根本不想四舍五入到 x 个小数位 - 您想四舍五入到 x 个有效数字。 因此,在您的示例中,您希望将 0.086 四舍五入到一位有效数字,而不是一位小数。
现在,由于双精度数的存储方式,使用双精度数并四舍五入到多个有效数字一开始就存在问题。 例如,您可以将 0.12 舍入为接近 0.1,但 0.1 并不能完全表示为双精度。 您确定实际上不应该使用小数吗? 或者,这实际上是为了显示目的吗? 如果是出于显示目的,我怀疑您实际上应该将双精度数直接转换为具有相关有效位数的字符串。
如果您能回答这些问题,我可以尝试提出一些合适的代码。 听起来很糟糕,通过将数字转换为“完整”字符串,然后找到第一个有效数字(然后在此之后采取适当的舍入操作),将数字转换为字符串,这可能是最好的方法。
It sounds to me like you don't want to round to x decimal places at all - you want to round to x significant digits. So in your example, you want to round 0.086 to one significant digit, not one decimal place.
Now, using a double and rounding to a number of significant digits is problematic to start with, due to the way doubles are stored. For instance, you could round 0.12 to something close to 0.1, but 0.1 isn't exactly representable as a double. Are you sure you shouldn't actually be using a decimal? Alternatively, is this actually for display purposes? If it's for display purposes, I suspect you should actually convert the double directly to a string with the relevant number of significant digits.
If you can answer those points, I can try to come up with some appropriate code. Awful as it sounds, converting to a number of significant digits as a string by converting the number to a "full" string and then finding the first significant digit (and then taking appropriate rounding action after that) may well be the best way to go.
如果是出于显示目的(正如您在 Jon Skeet 的答案的评论中所述),您应该使用 Gn 格式说明符。 其中 n 是有效数字的数量 - 正是您所追求的。
如果您想要 3 个有效数字,这里是用法示例(打印输出位于每行的注释中):
If it is for display purposes (as you state in the comment to Jon Skeet's answer), you should use Gn format specifier. Where n is the number of significant digits - exactly what you are after.
Here is the the example of usage if you want 3 significant digits (printed output is in the comment of each line):
我发现P爸爸和Eric的方法有两个bug。 例如,这解决了 Andrew Hancox 在本问答中提出的精度误差。 圆形方向也存在问题。 具有两位有效数字的 1050 不是 1000.0,而是 1100.0。 舍入是通过 MidpointRounding.AwayFromZero 修复的。
I found two bugs in the methods of P Daddy and Eric. This solves for example the precision error that was presented by Andrew Hancox in this Q&A. There was also a problem with round directions. 1050 with two significant figures isn't 1000.0, it's 1100.0. The rounding was fixed with MidpointRounding.AwayFromZero.
简而言之,这是一种可靠的解决方案。 它总是有效,其原因是它适用于字符串格式。 使用
Log
和Pow
你总是会被特殊值所困扰 - 没有解决办法,它很复杂。示例值表:
这是代码:
作为旁注 - 您可能对我在另一个问题下的工程符号答案感兴趣,这里。
Here is a solution that is - in one word - reliable. It just always works, and the reason for this is that it works with string formatting. With
Log
andPow
you will always be bitten by special values - there is no working around that, it's intricate.Table of example values:
Here is the code:
As a side note - you may be interested in my engineering notation answer under another question, here.
我同意 Jon 的评估的精神:
我需要对近似和非性能关键计算目的进行有效数字舍入,并且通过“G”格式进行格式解析往返就足够了:
I agree with the spirit of Jon's assessment:
I needed significant-digit rounding for approximate and non-performance-critical computational purposes, and the format-parse round-trip through "G" format is good enough:
双打上的 Math.Round() 存在缺陷(请参阅其文档中的调用者注释)。 稍后将四舍五入的数字乘以其十进制指数的步骤将在尾随数字中引入进一步的浮点错误。 像 @Rowanto 那样使用另一个 Round() 不会可靠地提供帮助,并且会遇到其他问题。 但是,如果您愿意使用十进制,那么 Math.Round() 是可靠的,乘以 10 和除以 10 的幂也是可靠的:
Math.Round() on doubles is flawed (see Notes to Callers in its documentation). The later step of multiplying the rounded number back up by its decimal exponent will introduce further floating point errors in the trailing digits. Using another Round() as @Rowanto does won't reliably help and suffers from other problems. However if you're willing to go via decimal then Math.Round() is reliable, as is multiplying and dividing by powers of 10:
这个问题与您提出的问题类似:
用显着数字格式化数字C# 中的数字
因此,您可以执行以下操作:
四舍五入到 1 个有效数字。
This question is similiar to the one you're asking:
Formatting numbers with significant figures in C#
Thus you could do the following:
Rounded to 1 significant digit.
设
inputNumber
为需要在小数点后进行significantDigitsRequired
转换的输入,则significantDigitsResult
就是下面伪代码的答案。Let
inputNumber
be input that needs to be converted withsignificantDigitsRequired
after decimal point, thensignificantDigitsResult
is the answer to the following pseudo code.在.NET 6.0上测试
我认为,由于框架的缺陷和浮点的误差,舍入结果不一致。 因此,使用时要小心。
例子:
Tested on .NET 6.0
In my opinion, the rounded results are inconsistent due to the defects of the framework and the error of the floating point. Therefore, be careful about use.
example:
正如 @Oliver Bock 所指出的那样,双打上的 Math.Round() 是有缺陷的(请参阅其 文档)。 稍后将四舍五入的数字乘以其十进制指数的步骤将在尾随数字中引入进一步的浮点错误。 一般来说,任何乘以或除以 10 的幂都会得到不精确的结果,因为浮点通常以二进制而不是十进制表示。
使用以下函数将避免尾随数字中的浮点错误:
但是,如果您愿意使用小数,那么 Math.Round() 是可靠的,乘以 10 和除以 10 的幂也是可靠的:
As pointed out by @Oliver Bock is that Math.Round() on doubles is flawed (see Notes to Callers in its documentation). The later step of multiplying the rounded number back up by its decimal exponent will introduce further floating point errors in the trailing digits. Generally, any multiplication by or division by a power of ten gives a non-exact result, since floating-point is typically represented in binary, not in decimal.
Using the following function will avoid floating point errors in the trailing digits:
However if you're willing to go via decimal then Math.Round() is reliable, as is multiplying and dividing by powers of 10:
对我来说,这个效果很好,并且对于负数也有效:
for me, this one works pretty fine and is also valid for negative numbers:
我的解决方案在某些情况下可能会有所帮助,我用它来显示大小差异很大的加密货币价格 - 它总是给我指定数量的有效数字,但与 ToString("G[位数]") 不同,它不显示科学记数法中的小值(不知道如何使用 ToString() 避免这种情况,如果有请告诉我!)
My solution may be helpful in some cases, I use it to display crypto prices which vary greatly in magnitude - it always gives me a specified number of significant figures but unlike ToString("G[number of digits]") it doesn't show small values in scientific notation (don't know a way to avoid this with ToString(), if there is then please let me know!)
这是一个受 Peter Mortensen 启发的版本,它为边缘情况(例如值为 NaN、Inf 或非常小的值)添加了一些保护措施:
Here's a version inspired by Peter Mortensen that adds a couple of safeguards for edge cases such as value being NaN, Inf or very small:
我已经做了:
I just did:
这是我在 C++ 中所做的事情,
希望我没有更改任何格式化它的内容。
Here is something I did in C++
Hopefully I did not change anything formatting it.