I tried formatting and have used several methods but excel always seems to round up the last three digits to something like this, 291827871268478000. Please how can this can be resolved. Previously, I usually worked with python to convert the file from csv to excel and the reference column ...
It is already a whole number, so no problem. 180*1.2*1.2 = 259.2 (Should round to 259, not too hard if using the round down feature) but if the person was to select that they want 5 { 180*1.2^5 }, this equals 447.8976 (round down would be 447) BUT if we were to take it ...
set@number_to_round=123.43set@number_to_round=@number_to_round+.001select@number_to_round[@number_to_round],round(@number_to_round,2)[rounded number]set@number_to_round=@number_to_round+.001select@number_to_round[@number_to_round],round(@number_to_round,2)[rounded number]set@number_t...
Yes. I guess another way of expressing my puzzlement is that Stata does not display, by default, to a greater number of decimal places. I don't know anything about this, but in Python, for instance, according to the documentation: "On a typical machine running Python, there are 53 bits...
If Python were to print the true decimal value of the binaryapproximation stored for 0.1, it would have to display: 0.1000000000000000055511151231257827021181583404541015625 So that's still quite a few zeros after the first 1. Compare that with Stata: ...
> > > Yes. I guess another way of expressing my puzzlement is that Stata does > not display, by default, to a greater number of decimal places. > > I don't know anything about this, but in Python, for instance, according > to the documentation: "On a typical machine running ...
would "force" Stata to store the zeros after 981? (or am I misunderstanding the whole issue?) Thanks Nick, -- Patrick Toche. References:http://docs.python.org/2/tutorial/floatingpoint.html On Thu, 10 Jan 2013 20:15:45 +0800, Nick Cox <njcoxstata@gmail.com>wrote: ...