On Wed, 4 May 2005, Duncan Murdoch wrote:
Vadim Ogranovich wrote:
-Original Message-
From: Prof Brian Ripley [mailto:[EMAIL PROTECTED] Sent: Wednesday,
April 27, 2005 1:13 AM
To: Vadim Ogranovich
Cc: Luke Tierney; r-devel@stat.math.ethz.ch
Subject: Re: [Rd] RE: [R] when can we expect
[1] 0.79 0.00 0.79 0.00 0.00
n = 1e6; iA = seq(2,n); x = double(n); system.time(for (i in iA) i)
[1] 0.24 0.01 0.24 0.00 0.00
Thanks,
Vadim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Luke Tierney
Sent: Friday, April 22, 2005 7:33 AM
To: Peter Dalg
On Wed, 6 Apr 2005 [EMAIL PROTECTED] wrote:
A while ago Luke Tierney remarked that the warning associated with
'makeActiveBinding'-- "saved workspaces with active bindings may not
work properly when loaded into older versions of R"-- should probably be
removed in R-devel. It
he
Representation of String Vectors". Is this something which is in works,
or planned, for future versions? It would be great if it were, this
should give R considerable speed boost.
This was considered at the time but is not on the table now.
luke
--
Luke Tierney
Chair, Statistics and Actuarial
.
configure ran fine, but `gmake' gave me a syntax error when compiling
src/main/memory.c. The offending line seems to be:
Rboolean success = FALSE;
Can anyone provide pointers?
(Just to make sure, I tried building it on our SLES9-x86_64 box, and that
passes make check.)
--
Luke Tierney
C
entirely my liability-- but
even ___documented___ features in R have been know to come & go a bit :) .
Nowadays I just expect to be buffetted by the winds of change every so often...
Mark
-Original Message-
From: Luke Tierney [mailto:[EMAIL PROTECTED]
Sent: Sat 12
R-devel@stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
--
Luke Tierney
Chair, Statistics and Actuarial Science
that actually only
describe the functions in the Rmpi package.
Can someone point me to some usefull guide?
For example, I would like to run a for-statement on
several processors (a subset of the statement on each
processor) but I can't figure out how to do this!
Thanks
--
Luke Tierney
Chair,
On Sat, 20 Feb 2005, Peter Dalgaard wrote:
Luke Tierney <[EMAIL PROTECTED]> writes:
For this specific case though, I _think_ the semantics we want is this:
eapply1 <- function(env, FUN, ..., all.names = FALSE) {
FUN <- match.fun(FUN)
lapply(.Internal(env2list(en
Thanks - any clues to follow up will be very helpful.
Nawaaz
__
R-devel@stat.math.ethz.ch mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Depart
On Fri, 18 Feb 2005, Peter Dalgaard wrote:
Luke Tierney <[EMAIL PROTECTED]> writes:
looks like eapply has an extra eval in the code. It does because the
code creates a call of the form
FUN()
with the literal value in place and then calls eval on this, which
results in calling eval on
use of this
would be less efficient that the current approach, but using
FUN(quote())
as the constructed call should do the trick.
[There seem to be a few other unnecessary eval's in cmputing the arguments
but I haven't thought this through yet]
luke
--
Luke Tierney
University
at they finally kicked the default up to 8M--good.
We still need to be a bit careful since running out of C stack will
cause a protection violation and there is no portabmle way to catch
this. But we can probably afford to loosen the defaults a bit.
luke
--
Luke Tierney
University of Io
he C pointer payload in a C routine), all "copies" are changed:
> >
> > > x <- as.tclObj(pi)
> > > x
> > 3.14159265359
> > > y <- x
> > > y
> > 3.14159265359
> > > mode(x)
> > [1] "externalptr"
> > >
er
print methods. On the other hand, the same issue exists with all
attributes on referece objects, so the safest approach is to use a
wrapper as Brian suggests.
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Department of Statistics andFax:
; RCC will work exactly as in interpreted R. This patch does not change
> the existing implementation in the default build; when enabled, it should
> not affect the evaluation of any R code except code compiled with RCC.
>
> John
>
> _________
ed in a workspace (they will be restored with NULL pointers).
Best,
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Department of Statistics andFax: 319-335-3017
Actuarial Science
241 Schaeffer Hall em
me));
}
else if(!(isString(name) && LENGTH(name) == 1))
error("invalid type or length for slot name");
...
The actual assignment uses setAttrib, which does operate in a way that
protects the value being assigned, but the unprotected allocation at
/**/ happens be
e the try()
> returns; could the old one be cleared at the time of the error, to
> avoid giving misleading information?
I'm not sure there aren't cases where clearing the traceback wouldn't
be more confusing. The current situation has a simple (and I think
fairly accurate) descri
ow done in C out into R where they are easier to maintain and could
then be automatically handled by an appropriate compiler back end.
Getting to a pure Java or pure .NET/mono setting is still likely to be
a fairly dauting task for a while.
Best,
luke
--
Luke Tierney
University of Iowa
> [EMAIL PROTECTED] mailing list
> https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
>
On Unix-like systems something like
> f<-pipe("wc",open="wb")
> save(list=ls(all=TRUE),file=f)
> close(f)
5 14 200
s
a design flaw in do.call
(though others disagree): It does an eval of it's arguents (on top of
what ordinary function calling does to evaluate the expression
producing the argument list). This is why there is no explicit eval
around the substitute. It is also why do.call isn't useful when
t allow people to edit the human-readable version directly if they
> prefer.
Duncan TL's suggestion to use Using R for the mark-up structure seems
very reasonable to me. Asking package authors to write in XML
directly, or anything that would make doing that the path of least
resistance,
rticular case but
otherwise defers to the function `start' in base then you can do that
too. If this is what you want then things would be clearer if you
used a different name, like
pgStart <- function (x, ...) {
if (is.Ttframed(x)) start(tframe(x), ...)
else start(x, ...)
}
If for
c
> os solaris2.8
> system sparc, solaris2.8
> status
> major1
> minor8.1
> year 2003
> month 11
> day 21
pose.
> >
> >
> > Gregory R. Warnes, Ph.D.
> > Senior Coordinator
> > Groton Non-Clinical Statistics
> > Pfizer Global Research and Development
> > <>
> >
> >
> > LEGAL NOTICE\ Unless expressly stated otherwise, this messag...{
Should be fixed in R-patched and R-devel.
Best,
luke
On Mon, 10 Nov 2003, Luke Tierney wrote:
> Thanks. Seems this slipped in while fixing another issue (surprising
> it wasn't noticed until now). Should be fixed in a day or two.
>
> Best,
>
> luke
>
> On S
age R
> > search()
> [1] ".GlobalEnv" "package:methods" "package:ctest" "package:mva"
> [5] "package:modreg" "package:nls" "package:ts" "Autoloads"
> [9] "package:base"
> >
>
>
> -roger
>
> _
least on our unix platforms.
>
> Luke Tierney <[EMAIL PROTECTED]> wrote:
> > Needs a call to R_CheckUserInterrupt at the appropriate place...
>
> Most unfortunate! Our system is like Martin's (Solaris 2.8, Emacs, ESS)
> and we also lose the use of ^C^C with R-1.8.0.
the two argument version or log10 generic might
lead to a situation where the basic relation log10(x) == log(x,10) ==
log(x)/log(10) is no longer true and code that depends on that
relationship will fail.
But it would be a good idea, once the design of methods stabilizes a
bit more, to
t only takes a minute or so,
> whereas our user here had a matrix that needed more than 10
> minutes of screen output !)
>
> __
> [EMAIL PROTECTED] mailing list
> https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
>
--
Luke Tier
ary
minus function applied to the positive value 1.
Bottom line: both formals and unlist are working as documented; code
that uses unlist(formals(...)) ans expects the result to be a numeric
vector needs to be changed.
Best,
luke
--
Luke Tierney
University of Iowa
the
reach a steady state. This is based on heuristics that work
reasonably well across a wide range of uses but might not be ideal for
really pushing the memory limit. At some point we might make some of
the tuning parameters for these heuristics available at the user
level, but this
gram.y with no overflow checking.
I've added some checking in R-devel, so these now give
> parse(text=paste(rep("x",5),collapse=""))
Error in parse(text = paste(rep("x", 5), collapse = "")) :
input buffer overflow
> formula
force the promise). I'd be careful fixing it though as it might
break other things.
Promises are really intended to support lazy evaluation and work best
if they are stored as values of variables in environments. I'm not
sure I would consider other uses reliable in the long run.
l directions of
improvement.
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Department of Statistics andFax: 319-335-3017
Actuarial Science
241 Schaeffer Hall email: [EMAIL PROTECTED]
Iowa City, IA 52242
t; > [1] 8119/5741 NaN 191/302 38804/47525
> > Warning message:
> > NaNs produced in: sqrt(xf)
> >
> > Bug, undocumented behaviour, feature? I dont know. It all seems to
> > work in 1.6.0, so everyone should downgrade now... :)
> >
> > Baz
> >
> > _
urnal of Multivariate Analysis, Journal of Statistical
> Software
> US mail: 9432 Boelter Hall, Box 951554, Los Angeles, CA 90095-1554
> phone (310)-825-9550; fax (310)-206-5658; email: [EMAIL PROTECTED]
> homepage: http://gifi.stat.ucla.edu
>
> ----
data structures and
memoizing calculations that are now repeated is likely to improve
performance substantially.
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Department of Statistics andFax: 319-335-3017
Actuarial Science
241
c()
> used (Mb) gc trigger (Mb)
> Ncells 370247 9.9 531268 14.2
> Vcells 87522 0.7 786432 6.0
>
You have managed to store Laurant's 140MB matrix in less than 1MB!:-)
If you use matrix(0, 600^2, 50) you get essentially the same pattern
as Laurant did.
>
On Tue, 1 Apr 2003, Luke Tierney wrote:
> On Tue, 1 Apr 2003, John Chambers wrote:
>
> > I think this is a consequence of the extra context added to make methods
> > work right with R lexical scoping, namespaces, etc. Or a subtlety in
> > R's definition of missi
's happening. But as to why, we need some expert
> help! (Luke?)
We need a bit more info transferred across from the generic and we
need to reset the environments of the promises for missing arguments.
I'll look into it.
luke
--
Luke Tierney
University of Iowa
s right. It may be that for some reason on this setup you
need to give gcc something like -Wl,-E instead of -export-dynamic in
the linker flags.
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Department of Statistics andFax: 31
On Tue, 28 Jan 2003, Henrik Bengtsson wrote:
> First of all, I haven't followed the discussion about the new/upcoming
> name space support in R so I do not know the purposes or requirements
> for it, neither its design, and I can only guess. I found the (initial?)
> notes by Lu
to implementation
details, just the funtionality.) I would prefer not to add separate
control over frame dumping; fine control like that is I think better
left to the error handling system.
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Departm
ng(myarg)) {
## ok, it's there, do whatever
}
i.e. just remove the things you explicitly want not in ... by naming
them as arguments work for your setting?
luke
--
Luke Tierney
University of Iowa Phone: 319-335-3386
Department
46 matches
Mail list logo
