query: SetPrecision on a decimal gives imprecise result
positive_passages.docid: 156554
positive_passages.text: N not behaving in the way I expected it would
negative_passages.docid: 9540
negative_passages.text: Output precision
negative_passages.docid: 94139
negative_passages.text: Why SetOptions[$FrontEnd, PrintPrecision -> 16] affects one plot ticks but not the other?
negative_passages.docid: 80320
negative_passages.text: When can I assume that all decimal digits returned by Mathematica are provably correct?
negative_passages.docid: 59342
negative_passages.text: My floating point number has extra digits when I print it
negative_passages.docid: 24378
negative_passages.text: Strange behavior of MachinePrecision
negative_passages.docid: 132370
negative_passages.text: Why does Java shows extra values after float calculation?
negative_passages.docid: 152537
negative_passages.text: Precision error with floats in Java
negative_passages.docid: 81719
negative_passages.text: Very different results from evaluating same expression with different precisions
negative_passages.docid: 125068
negative_passages.text: How to round up a decimal?
negative_passages.docid: 26320
negative_passages.text: Is there a way to round a decimal place to the nearest whole in javascript?
negative_passages.docid: 137025
negative_passages.text: JavaScript 64 bit numeric precision
negative_passages.docid: 38768
negative_passages.text: Python/numpy floating-point text precision
negative_passages.docid: 10912
negative_passages.text: Changing precision on a column in the attribute table without losing data?
negative_passages.docid: 123170
negative_passages.text: Is it possible to change the precision in Compile?
negative_passages.docid: 51743
negative_passages.text: QTableView: change precision for double values
negative_passages.docid: 23412
negative_passages.text: How is a ROCAUC=1.0 possible with imperfect accuracy?