On 2/4/2009 2:27 PM, Terry Therneau wrote:
Lots of interesting comments while I was off in meetings. (Some days I wonder
why they pay me - with so many meetings I certainly don't accomplish any work.)
Some responses:
1. To Brian: I think that there is another issue outside of save(). Use t
Lots of interesting comments while I was off in meetings. (Some days I wonder
why they pay me - with so many meetings I certainly don't accomplish any work.)
Some responses:
1. To Brian: I think that there is another issue outside of save(). Use the
frailty.gamma function as a thought examp
On 2/4/2009 10:57 AM, l...@stat.uiowa.edu wrote:
On Wed, 4 Feb 2009, Duncan Murdoch wrote:
One correction below, and a suggested alternative approach.
On 2/4/2009 9:31 AM, Terry Therneau wrote:
In R, functions remember their entire calling chain. The good thing
about this is that they can
On Wed, 4 Feb 2009, Duncan Murdoch wrote:
One correction below, and a suggested alternative approach.
On 2/4/2009 9:31 AM, Terry Therneau wrote:
In R, functions remember their entire calling chain. The good thing
about this is that they can find variables further up in the nested
context,
One correction below, and a suggested alternative approach.
On 2/4/2009 9:31 AM, Terry Therneau wrote:
In R, functions remember their entire calling chain. The good thing about
this is that they can find variables further up in the nested context, i.e.,
mfun <- function(x) { x+y}
will lo
Brian R makes good points.
I made a mistake in the prior post, it should have said
new.env(parent=globalenv())
for pspline. You want the saved function to pay attention to the search()
path.
This is what is actually in the code, I was guilty of mistyping.
If the print function
You need to set the environment to the rpart namespace, at least in
the print etc functions attached to the return object. One reason is
that formatg needs to be found, and in principle that has to be right
as you are just going a couple of steps up the environment chain.
I've not had time to
In R, functions remember their entire calling chain. The good thing about
this is that they can find variables further up in the nested context, i.e.,
mfun <- function(x) { x+y}
will look for 'y' in the function that called myfun, then in the function that
called the function, on up an
Dear Prof. Ripley,
Thanks for the quick reply.
I do notice an in the print output. I assume it is
used to keep copies of the initial data used for the model.
- Is it safe to assume that it would not affect any other
functionality, apart from the usage of those particular functions?
- Is there
On Tue, 3 Feb 2009, tan wrote:
I am using rpart to build a model for later predictions. To save the
prediction across restarts and share the data across nodes I have been
using "save" to persist the result of rpart to a file and "load" it
later. But the saved size was becoming unusually large (e
I am using rpart to build a model for later predictions. To save the
prediction across restarts and share the data across nodes I have been
using "save" to persist the result of rpart to a file and "load" it
later. But the saved size was becoming unusually large (even with
binary, compressed mode).
11 matches
Mail list logo
