Displaying 20 results from an estimated 8000 matches similar to: "dget not restoring dput in R 2.6.0 (PR#10350)"
2004 Jul 15
1
dput and dget
I am seeking advice about dput() and dget().
We are using the ascii format supported by these functions as a way to
write data from other programs that can be read into R easily. We are able
to save complicated results (in the form of an R list) to a single file
that can be read trivially into R or S-Plus.
My question is whether that format can be considered a safe one for
medium-term (say
2007 Apr 22
1
dput/dget when a data frame has 2 rows (PR#9627)
This doesn't seem right; I'm using R version 2.4.1 (2006-12-18) on Mac OS
and Win XP and find the same issue:
> mydataframe <- data.frame(ppi=c(.5,.5),mmu=c(5,10))
> dput(mydataframe,"mydataframe.txt")
> dget("mydataframe.txt")
Error in attributes(.Data) <- c(attributes(.Data), attrib) :
row names must be 'character' or 'integer', not
2006 Oct 10
1
error in dput applied to dataframe (PR#9286)
Full_Name: Daniel F Higgins
Version: 2.4.0
OS: Windows XP and Mac OSX
Submission from: (NULL) (128.111.242.49)
Create a dataframe as indicated below and apply 'dput' to it; note that the
row.names attribute is incorrect!
> aaa <- c("AAA","BBB","AAA")
> bbb <- c(1,2,3)
> df <- data.frame(aaa,bbb)
> dput(df)
structure(list(aaa =
2014 Jun 20
1
dget() much slower in recent R versions
Hello,
I've noticed that dget() is much slower in the current and devel R
versions than in previous versions. In 2.15 reading a 10000-row
data.frame takes less than half a second:
> (which.r <- R.Version()$version.string)
[1] "R version 2.15.2 (2012-10-26)"
> x <- data.frame(matrix(sample(letters, 100000, replace = TRUE), ncol = 10))
> dput(x, which.r)
>
2018 Sep 29
1
Improvement to documentation in dput.Rd
If the "Matrix" package is attached, 'example(dget)' fails:
> library(Matrix)
> example(dget)
dget> fil <- tempfile()
dget> ## Write an ASCII version of function mean to our temp file
dget> dput(mean, fil)
dget> ## And read it back into 'bar'
dget> bar <- dget(fil)
Error in initialize(value, ...) : '...' used in
1999 Feb 12
1
more on dput
I would like to write data so that I can re-read it and reproduce results,
preferably in both R and Splus. In the past when I have done this my data has
been relatively simple and I've just scan()ed it. Now I have a fairly
complicated structure I would like to preserve and I've been trying to use dput
and dget. Is there a better way? If not, the following truncation by dput,
which I
1999 May 27
1
Factor structures not preserved after dump/dput (PR#200)
Full_Name: Marek Ancukiewicz
Version: 0.64.0
OS: Linux (RedHat 6.0)
Submission from: (NULL) (132.183.12.87)
I've noticed that factor structures get recoded when the data is dumped
using either dump or dput and then restored with source or dget. This
occurs when the values taken by factors do not include 1. For example:
a <-
2007 Feb 28
1
Help with "row.names = as.integer(c(NA, 5))" in file from dput
I am trying to understand why syntax used by dput() to write
rownames is valid (say, when read by dget()). I ask this
because I desire to emulate its actions *reliably* in my For2R
routines, and I won't be comfortable until I understand what R
is doing.
Given data set "fred":
> fred
id var1
1 1991 0.4388587
2 1992 0.8772471
3 1993 0.6230486
4 1994 0.2340929
5 1995
2003 Sep 30
2
dump/source problem with hclust object (PR#4361)
library(mva)
data(USArrests)
hc <- hclust(dist(USArrests), "ave")
plot(hc) # OK
dump(c("hc"), "tst")
rm(hc)
source("tst")
plot(hc) # Error in plot.hclust(hc) : invalid dendrogram input
The same problem occurs with dput/dget
--please do not edit the information below--
Version:
platform =
2008 Aug 20
2
Reading in a value of .Random.seed in .Rprofile
For reasons that are best known to myself [ ;-) ] I have a value
of .Random.seed
saved (via dput()) in a file ``.Random.seed.save''.
In my .Rprofile I have the lines:
.Random.seed <- dget(".Random.seed.save")
Junk <- dget(".Random.seed.save")
print(all.equal(.Random.seed,dget(".Random.seed.save")))
2007 Jan 04
1
littler+dget+stdin -> segmentation fault
Hi, I'm trying to write a series of pipes using littler, and I get the
following behaviour: Sorry if I'm just doing something witless, I'm new to
R. I'm using the latest versions from debian testing (2.4.0 and 0.0.8).
$ r -e 'a<-dget(file=stdin()); print(a)'
?list(a=2)
Segmentation fault
In R itself this works:
> dget(file=stdin())
?list(a=2)
$a
[1] 2
As do (from
2020 Oct 20
0
write.csv covert Åland to <c5>land
Hi there,
Why the same string is displayed in different form?
> abc[,1]
[1] "?land" "Afghanistan"
> abc
name
1 <c5>land
2 Afghanistan
And more...
> dput(abc, "aa.txt")
> dget("aa.txt")
name
1 <c5>land
2 Afghanistan
> dget("aa.txt")[,1]
[1] "<c5>land"
2004 Aug 25
5
S <-> R
Hello! I would like to be able to read in list data objects in R/S
created in R/S. (Ie R->S or S->R.) I have tried 'dput' and 'dump' in S,
but neither of the created files could be read into R (with 'dget' nor
'source'). Is there any way that I can save a list object in S that can
be read into R?
Sincerely,
Zachary Skrivanek, PhD
Research Scientist
2006 Nov 08
1
error message for row names
Hi R users -
I got an error message when reading in a saved file (a list structure)
>dget("REPLICATION001")
Error in attributes(.Data) <- c(attributes(.Data), attrib) :
row names must be 'character' or 'integer', not 'double'
I don't need row names and didn't even specify row names when I saved the
file. What do I need to do for reading
2020 Oct 20
1
write.csv covert Åland to <c5>land
It looks like an encoding problem.
It works fine for me with R encoding set to UTF-8
Here is part of my sessionInfo() results
[1] LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=C
[3] LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8
[5] LC_MONETARY=en_CA.UTF-8 LC_MESSAGES=en_CA.UTF-8
I would suggest issuing the command
sessionInfo()
and seeing what your encoding is.
On Tue, 20 Oct 2020 at 08:22,
2020 Oct 20
1
write.csv covert Åland to <c5>land
You don't say, but I'd guess you're using Windows. In your code page,
the character ? is probably not representable. At some point in the
sequence of operations involved in printing the dataframe R puts the
string into the native encoding, and since that's impossible on your
system, it substitutes the <c5> instead. The fact that you can
sometimes display it is because
2009 Mar 23
2
dput(as.list(function...)...) bug
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 ,
2006 Nov 23
1
dumping/loading objects with 'tsp' attribute
Dear all,
I'm indirectly faced with the fact that setting the 'tsp' attribute of
an object modifies its class definition:
> class( structure(1:2, tsp=c(1,2,1), class=c("myts","ts")) )
[1] "ts" "myts"
In general, this is of really little (ok, I admit: totally no)
interest for me because 'myts' class is added just after assigning the
2011 Mar 15
1
Performance with XP64
What sort of performance is expected over GigE, with Samba 3 as the
server and XP64 as the client? I havn't been able to find any current
benchmarks at all.
http://lists.samba.org/archive/samba/2010-June/156708.html talks about
the same configuration, and suggests that the protocol should be able
to break 100MB/sec. (Unfortunately, the poster disappeared without
following up.) Focusing on
2020 Feb 29
2
dput()
Thanks guys, I guess I should have referred to FAQ 7.31 (which I am
indeed very familiar with) to avoid misunderstanding. I have always
used dput() to clarify 7.31-type issues.
The description in ?dput implies [to me at any rate] that there will
be no floating-point roundoff in its output. I hadn't realised that
'deparsing' as discussed in dput.Rd includes precision roundoff
issues.