search for: deparseopts

...tion of control > > = c("all", "hexNumeric") looks good and I will experiment > > with this. > > This was not Duncan's suggestion but rather Duncan's *citation* : > Note that he used " .... " ! > > The citation is from ?deparseOpts (to which one is pointed when reading ?dput), > <rant> > but unfortunately many people nowadays have stopped reading texts > that are longer than a tweet... ;-) > <rant/> > ... and indeed, ?dput and ?deparse use 'control = "all"' > instead of...

...packages). I agree that this is > > surprising (to me). > > > > To reframe this question: is there way to get an *exact* ASCII > > representation of a numeric value (i.e., guaranteeing the restored value > > is identical() to the original) ? > > > > .deparseOpts has > > > > ?"digits17"?: Real and finite complex numbers are output using > > format ?"%.17g"? which may give more precision than the > > default (but the output will depend on the platform and there > > may be loss...

...2.7 143.12 92.7 "type.convert" 9.52 6.2 9.52 6.2 "read.table" 1.60 1.0 154.28 99.9 "paste" 0.02 0.0 0.08 0.1 "textConnection" 0.02 0.0 0.04 0.0 ".deparseOpts" 0.02 0.0 0.02 0.0 "file" 0.02 0.0 0.02 0.0 "make.names" 0.02 0.0 0.02 0.0 "print.default" 0.02 0.0 0.02 0.0 "read.delim" 0.00 0.0...

...ed to me). Also, Duncan's suggestion of control > = c("all", "hexNumeric") looks good and I will experiment > with this. This was not Duncan's suggestion but rather Duncan's *citation* : Note that he used " .... " ! The citation is from ?deparseOpts (to which one is pointed when reading ?dput), <rant> but unfortunately many people nowadays have stopped reading texts that are longer than a tweet... ;-) <rant/> ... and indeed, ?dput and ?deparse use 'control = "all"' instead of c("all", "hex...

...6 2.16 0.6 ! 1.92 0.6 1.92 0.6 %in% 1.86 0.5 25.48 7.5 switch 1.68 0.5 1.76 0.5 names<- 1.56 0.5 1.78 0.5 < 1.54 0.5 1.54 0.5 .deparseOpts 1.50 0.4 11.98 3.5 match.call 1.48 0.4 2.84 0.8 .Call 1.34 0.4 1.34 0.4 is.na 1.30 0.4 1.30 0.4 all 1.24 0.4 1.48 0.4 formals 1.22 0.4 2.4...

...l", "hexNumeric") looks good and I will experiment >> > with this. >> >> This was not Duncan's suggestion but rather Duncan's *citation* : >> Note that he used " .... " ! >> >> The citation is from ?deparseOpts (to which one is pointed when reading ?dput), >> <rant> >> but unfortunately many people nowadays have stopped reading texts >> that are longer than a tweet... ;-) >> <rant/> >> ... and indeed, ?dput and ?deparse use 'control...

My two matrices are roughly the sizes of m1 and m2. I tried using two apply and cor.test to compute the correlation p.values. More than an hour, and the codes are still running. Please help to make it more efficient. m1 <- matrix(rnorm(100000), ncol=100) m2 <- matrix(rnorm(10000000), ncol=100) cor.pvalues <- apply(m1, 1, function(x) { apply(m2, 1, function(y) { cor.test(x,y)$p.value

...floating point (author of 'Brobdingnag', among other numerical packages). I agree that this is surprising (to me). To reframe this question: is there way to get an *exact* ASCII representation of a numeric value (i.e., guaranteeing the restored value is identical() to the original) ? .deparseOpts has ?"digits17"?: Real and finite complex numbers are output using format ?"%.17g"? which may give more precision than the default (but the output will depend on the platform and there may be loss of precision when read back). ... but this still...

...quot; 8.92 1.64 14.50 2.67 "svd" 8.70 1.60 185.88 34.19 "mpinv" 8.40 1.55 221.56 40.76 "c" 8.16 1.50 8.16 1.50 ".deparseOpts" 7.92 1.46 12.42 2.28 "$" 6.94 1.28 6.94 1.28 "t.default" 6.70 1.23 6.70 1.23 "diag" 5.66 1.04 8.96 1.65 &q...

...ngnag', among other numerical packages). I agree that this is > surprising (to me). > > To reframe this question: is there way to get an *exact* ASCII > representation of a numeric value (i.e., guaranteeing the restored value > is identical() to the original) ? > > .deparseOpts has > > ?"digits17"?: Real and finite complex numbers are output using > format ?"%.17g"? which may give more precision than the > default (but the output will depend on the platform and there > may be loss of precision when read...

...tering directory `/home/btyner/R-3.1.1/src/library/tools/src' make[6]: Leaving directory `/home/btyner/R-3.1.1/src/library/tools/src' make[5]: Leaving directory `/home/btyner/R-3.1.1/src/library/tools/src' make[4]: Leaving directory `/home/btyner/R-3.1.1/src/library/tools' Error in .deparseOpts(control) : could not find function "anyNA" Calls: ::: ... tryCatch -> tryCatchList -> tryCatchOne -> <Anonymous> Execution halted make[3]: *** [all] Error 1 make[3]: Leaving directory `/home/btyner/R-3.1.1/src/library/tools' make[2]: *** [R] Error 1 make[2]: Leaving dir...

...nce() a no-op and hence 1+2+4+8 = 15 turns off all "browsing/debugging" for which I'd typically want a convenient short cut. for back compatibility, FALSE = 1 TRUE = 0 I'd use UI with a vector of character strings, that can be translated to integer codes entirely analogous to .deparseOpts() {used from deparse(), dput() and dump()}. ----- A considerably simpler interface which would be good enough for my use, was to simply add a new debuggingState() function with TRUE/FALSE option, and we would just have to decide how much "turning off debugging" should happen when the...

Tested in R 2.8.1 Windows > ff <- formals(function(x)1) > ff1 <- as.list(function(x)1)[1] # ff1 acts the same as ff in the examples below, but is a list rather than a pairlist > dput( ff , control=c("warnIncomplete")) list(x = ) This string is not parsable, but dput does not give a warning as specified. > dput( ff ,

My interpretation of dput.Rd is that dput() gives an exact ASCII form of the internal representation of an R object. But: rhankin at cuttlefish:~ $ R --version R version 3.6.2 (2019-12-12) -- "Dark and Stormy Night" Copyright (C) 2019 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) [snip] rhankin at cuttlefish:~ $ R --vanilla --quiet > x <-

...and hence over 16Gb of heap is in use): it now reports NA. (PR#9345) o rapply() now detects more user errors in supplying arguments. (PR#9349) o boxplot() was ignoring argument 'boxfill'. (PR#9352) o plot.lm(which = 6, id.n = 0) did not work. (PR#9333) o .deparseOpts("delayPromises") was not matching the C code, returning 64 rather than 32. o bxp() could use partial matching on 'pars' when finding defaults for some of its parameters, e.g. a setting of 'cex.axis' in 'pars' or inline was used to set...

...and hence over 16Gb of heap is in use): it now reports NA. (PR#9345) o rapply() now detects more user errors in supplying arguments. (PR#9349) o boxplot() was ignoring argument 'boxfill'. (PR#9352) o plot.lm(which = 6, id.n = 0) did not work. (PR#9333) o .deparseOpts("delayPromises") was not matching the C code, returning 64 rather than 32. o bxp() could use partial matching on 'pars' when finding defaults for some of its parameters, e.g. a setting of 'cex.axis' in 'pars' or inline was used to set...

...> 2. . 8.8 FUN > 3. . . 8.8 apply > 4. . . . 8.7 FUN > 5. . . . . 8.6 cor.test > 6. . . . . . 8.4 cor.test.default > 7. . . . . . . 2.4 match.arg > 8. . . . . . . . 1.7 eval > 9. . . . . . . . . 1.4 deparse > 10. . . . . . . . . . 0.6 .deparseOpts > 11. . . . . . . . . . . 0.2 pmatch > 11. . . . . . . . . . . 0.1 sum > 10. . . . . . . . . . 0.5 %in% > 11. . . . . . . . . . . 0.3 match > 12. . . . . . . . . . . . 0.3 is.factor > 13. . . . . . . . . . . . . 0.3 inherits > 8. . . . . . . . 0.2 fo...

...ngOnly' argument to be used in conjunction with --args. o contour() now passes graphical parameters in '...' to axis() and box(). o New data set 'crimtab' on Student(1908)'s 3000 criminals. o cut.default() has a new argument 'ordered_result'. o .deparseOpts() has two new options: "keepNA" to ensure that different types (logical, integer, double, character and complex) of NAs are distinguished, and "S_compatible" to suppress the use of R-specific features such as 123L and to deparse integer values of a double vector with a trail...

...ngOnly' argument to be used in conjunction with --args. o contour() now passes graphical parameters in '...' to axis() and box(). o New data set 'crimtab' on Student(1908)'s 3000 criminals. o cut.default() has a new argument 'ordered_result'. o .deparseOpts() has two new options: "keepNA" to ensure that different types (logical, integer, double, character and complex) of NAs are distinguished, and "S_compatible" to suppress the use of R-specific features such as 123L and to deparse integer values of a double vector with a trail...

...tically from deparsed code. dput(), deparse() and dump() now print the names() information only once, using the more readable (tag = value) syntax, notably for list()s, i.e., including data frames. These functions gain a new control option "niceNames" (see .deparseOpts()), which when set (as by default) also uses the (tag = value) syntax for atomic vectors. On the other hand, without deparse options "showAttributes" and "niceNames", names are no longer shown also for lists. as.character(list( c (one = 1))) now include...