Dear Bill, dear all,
yes that seems to be it. The problem orginates from objects of class
transformMap from package flowCore
> object_size(object@transforms@transforms$PC1.all@f)
174 MB
> object.size(object@transforms@transforms$PC1.all@f)
1160 bytes
object@transforms@transforms$PC1.all@f
Also, note that the function
function(x) x
has no free variables so it doesn't matter what environment encloses it.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Wed, Feb 20, 2019 at 7:47 AM William Dunlap wrote:
> object@transforms@transforms$PC1.all@f
> function(x) x
>
> Do you
object@transforms@transforms$PC1.all@f
function(x) x
Do you know how to 'see' what's in 0x3314db8 ?
ls.str(all=TRUE, environment(object@transforms@transforms$PC1.all@f)
will list the names, types, summaries, etc. of the objects in that
environment.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
One reason save() makes bigger files than dump() is that save() saves
environments associated with functions that are saved and those
environments may contain large datasets that are not really needed.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Tue, Feb 19, 2019 at 11:59 AM Jeff Newmiller
Make a reproducible example that focuses on the save/load aspect of the size
problem. You may need to experiment with which variables need to be in the save
file in order to trigger the behavior. Your example might have to involve
sending us a link to a large file, but that size may dissuade
2:51 PM
To: r-help@r-project.org
Subject: [R] Save creates huge files, dump doesn't
Dear list,
I noticed an extremely odd behavior... I have a rather complex shiny app which
allows the user to store his/her state which internally obviously triggers as
call to save as follows save(list=c("
Dear list,
I noticed an extremely odd behavior... I have a rather complex shiny app which
allows the user to store his/her state which internally obviously triggers as
call to save as follows
save(list=c("plots","gates","populations","cg", "genelists","colorscores",
"proj",
7 matches
Mail list logo
