search for: 53bit

Displaying 4 results from an estimated 4 matches for "53bit".

Did you mean: 3bit
2018 May 09
0
NAs produced by integer overflow, but only some time ...
...ision constants are numeric with no decoration (e.g. 61224). Integer constants have an L (e.g. 61224L). c) 61224*61224 > 2^31-1 so that answer cannot fit into an integer. d) Exponentiation is a floating point operation so the result of 61224L^2L is a floating point answer that CAN fit into the 53bit mantissa of a double precision value, so no overflow occurs. e) Defining a function like yules.k1 and never showing how you called it does not constitute a reproducible example. To avoid such gaffes you can use the reprex package to confirm that the errors shown in your question are in fact reprod...
2018 May 09
2
NAs produced by integer overflow, but only some time ...
...nstants are numeric with no decoration (e.g. 61224). Integer constants have an L (e.g. 61224L). > c) 61224*61224 > 2^31-1 so that answer cannot fit into an integer. > d) Exponentiation is a floating point operation so the result of 61224L^2L is a floating point answer that CAN fit into the 53bit mantissa of a double precision value, so no overflow occurs. Yes, that's all great and I knew that from <https://stackoverflow.com/questions/8804779/what-is-integer-overflow-in-r-and-how-can-it-happen>. > e) Defining a function like yules.k1 and never showing how you called it does no...
2018 May 09
3
NAs produced by integer overflow, but only some time ...
I have problem with integer overflow that I cannot understand. I have a character vector curr.lemmas with the following properties: length(curr.lemmas) # 61224 length(unique(curr.lemmas)) # 2652 That vector is the input to the following function: yules.k1 <- function(input) { m1 <- length(input); temp <- table(table(input)) m2 <- sum("*"(temp,
2018 May 09
1
NAs produced by integer overflow, but only some time ...
...with no decoration (e.g. 61224). > Integer constants have an L (e.g. 61224L). > > c) 61224*61224 > 2^31-1 so that answer cannot fit into an integer. > > d) Exponentiation is a floating point operation so the result of 61224L^2L > is a floating point answer that CAN fit into the 53bit mantissa of a double > precision value, so no overflow occurs. > > e) Defining a function like yules.k1 and never showing how you called it > does not constitute a reproducible example. To avoid such gaffes you can > use the reprex package to confirm that the errors shown in your que...