>
> From: Philippe Grosjean <[EMAIL PROTECTED]>
>
> However, I was suprised to learn that the Pipeline Pilot R Collection is
> not GPL and is not free (in term of money, i.e., you have to pay
> 3500$/year to use it). I am not sure, but I think they break the GPL
> license here since they use a comm
I should also make it clear -- while I reported non-fatal stack errors
in the first thread, I'm not seeing them any more, just the core dump.
On 4/19/06, A.J. Rossini <[EMAIL PROTECTED]> wrote:
> I'm going to recode the sequence in C tommorow (I'm in Seattle right
> n
a, but not sure when I'll get the laptop connected again).
On 4/19/06, A.J. Rossini <[EMAIL PROTECTED]> wrote:
> It doesn't seem to help. I suspect it is more related to signal
> handling changes than the stack. Note that I dropped that from the
> subject line for my email
t; wrote:
> Tony,
>
> It is possible to turn stack checking off by setting R_CStackLimit = -1 in
> the embedding application: it works for me, so can you please try it?
>
> Brian
>
> On Wed, 19 Apr 2006, A.J. Rossini wrote:
>
> > Well, nothing has changed in the issues
Well, nothing has changed in the issues that I brought up earlier,
except that I can confirm core dumps in non-threaded lisps as well
(CLISP), using svn version 37840 (this morning, Seattle time) for
R-2-3-patches. I've not tried Thomas' suggested fixes, as I'm
hesistant to go down the road of fi
I'm pretty sure that we've fixed that problem. (I'm merging 2 different
CL/R trees together, one of which is Cyrus's). An alternative fix patched
R to undo that, but that's not kosher.
best,
-tony
On 4/12/06, Thomas Lumley <[EMAIL PROTECTED]> wrote:
>
&
On 4/12/06, Simon Urbanek <[EMAIL PROTECTED]> wrote:
> On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
>
> > I've been experiencing some interesting stack warnings recently
> > when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
> > series. In
On 4/11/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Apr 2006, A.J. Rossini wrote:
>
> > I will say this first -- I can't copy/paste the error message from the
> > screen, so it's being retyped. Errors might occur. SORRY.
> >
> >
st to eliminate things, is the host application
> in which R is being embedded doing anything with
> the stack, e.g. some lisp system playing with threads
> via manipulating the stack?
>
> D.
>
>
> A.J. Rossini wrote:
> > I will say this first -- I can't copy/
On 4/11/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Apr 2006, A.J. Rossini wrote:
>
> > I will say this first -- I can't copy/paste the error message from the
> > screen, so it's being retyped. Errors might occur. SORRY.
> >
> >
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing some interesting stack warnings recently when
moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0 series. In
particular, I'm getting warn
> From: Ross Boylan <[EMAIL PROTECTED]>
>
> In answer to the other question about using OS checkpointing
> facilities, I haven't tried them since the application will be running
> on a cluster. More precisely, the optimization will be driven from a
> single machine, but the calculation of the obj
> -- Forwarded message --
> From: Byron Ellis <[EMAIL PROTECTED]>
> If we wanted to be truly radical we'd just accept that graphics
> devices and event loops are just special cases of the connection and
> merge the whole thing, thus more-or-less reinventing CLIM. :-)
Eventually, a
c++ stuff is left out from the new tar ball.
>
> And I have also been corrected: most of the work on the cross-
> compiling tools were in fact done by Brian Ripley.
>
> Kasper
>
> On Oct 18, 2005, at 10:45 AM, A.J. Rossini wrote:
>
> > Technically, "Jun Yan,
Technically, "Jun Yan, based on work and documentation most likely by
Brian Ripley, with Tony prodding Jun". Though I'm sure even that
would be corrected.
Sorry, no clue, as I'm not using R nor Linux at work these days. I'm
sure someone else knows.
On 10/18/05, Kasper Daniel Hansen <[EMAIL PRO
I fully support Duncan M (though it's painless for me).
What I wanted to do, and explored, when I was visiting Peter D in
Copenhagen nearly 2 years ago, was to XML-ize the output stream, so
that I could mark it up. From that, it would be reasonably simple to
parse output (provided you marked it u
Interesting.
So, we've got lots of people that want GUIs, lots of variants with
existing prototypes, and lots of clamor for skilled collaborators.
As most of the work has seemed to be of the "I know this, and this is
what I want to do", it will be interesting to see how it shakes out.
I've still
;ash_1.0-9', not 'ash', and I was referring you to the
> authors (and RG was one and will know who else was involved, as I recall
> at least Jeff Gentry) as to their intentions.
>
>
> On Tue, 4 Oct 2005, A.J. Rossini wrote:
>
> > On 04 Oct 2005 16:42:14 +
On 04 Oct 2005 16:42:14 +0200, Peter Dalgaard <[EMAIL PROTECTED]> wrote:
>
> > > > The issue is that installed.packages() has never been taught about
> > > > versioned installs, and you might like to take that up with your BioC
> > > > colleagues who
Also, I don't know what this has to do with BioC. This is core R, so
pertinent to this list. Otherwise, perhaps it should be taken out?
On 10/4/05, A.J. Rossini <[EMAIL PROTECTED]> wrote:
> I expect "new.packages()" to not report on packages which I've
>
ed ash and then installed it with version. new.packages() showed
> it as new in both 2.1.1 and 2.2.0-beta.
>
> The issue is that installed.packages() has never been taught about
> versioned installs, and you might like to take that up with your BioC
> colleagues who added the idea.
>
gt; Deepayan). That has
>
> .onLoad <- function(lib, pkg)
> {
> library.dynam(pkg, pkg, lib )
> lattice.options(.defaultLatticeOptions())
> lattice.setStatus(.defaultLatticeStatus())
> }
>
> which is incorrect: it should be library.dynam("lattice"
R-devel, SVN revision 35729 (this morning, euro-time)
So far, I'm having awful luck with the "installWithVers" flags.
Recent example:
I can install.packages("lattice", installWithVers=TRUE)
successfully (no errors, at least it looks like a successful install),
but can't load it:
Error in librar
In Rdevel, SVN version built this morning around 10am central european
time, it looks like
install.packages(new.packages(),installWithVers=TRUE)
seem to ignore the version information -- that is, it reinstalls
current versions of packages.
This did not happen before I used "installWithVers=TR
It might be my settings or improper use -- but if I use the
"installWithVers=TRUE" flag for update.packages(), I don't seem to get
updates;
and if I use "install.packages(new.packages(),installWithVers=TRUE)",
it seems to (re-)install identical versions of what I have.
(this is with Rdevel from su
r-project.org/gR/.
> Have you looked at the "dynamicGraph" package?
>
might also look at the graph packages (graph, RBGL, etc) in BioConductor.
best,
-tony
"Commit early,commit often, and commit in a repository from which we can easily
roll-back your mistakes" (AJR, 4J
t colleague,
with respect to corporate packaging of R: "So they (corporate
packagers) just pick some version and package it, right?" and my
flabbergasted response was:
"and so, what the heck do you think they (corporate packagers) do with
SAS, S-PLUS, and SPSS, and why do you think it's different...?").
best,
-tony
"Commit early,commit often, and commit in a repository from which we can easily
roll-back your mistakes" (AJR, 4Jan05).
A.J. Rossini
[EMAIL PROTECTED]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
27 matches
Mail list logo
