> Qin Zhu
> on Mon, 2 May 2016 16:19:44 -0400 writes:
> Hi,
> I’m working on a Shiny app for statistical analysis. I ran into this
"maximal number of DLLs reached" issue recently because my app requires
importing many other packages.
> I’ve posted my question on stackov
On 04/05/2016 08:44, Martin Maechler wrote:
Qin Zhu
on Mon, 2 May 2016 16:19:44 -0400 writes:
> Hi,
> I’m working on a Shiny app for statistical analysis. I ran into this "maximal
number of DLLs reached" issue recently because my app requires importing many other
packages.
I think this issue will be of interest to the list. It seems like a
problem with nlme, and I was drawn into it because of a collaborator
who encountered this issue in a simple experiment and wound up
questioning the mixed model approach to his question.
The issue is that lme, when faced with certa
On 05/04/2016 05:15 AM, Prof Brian Ripley wrote:
On 04/05/2016 08:44, Martin Maechler wrote:
Qin Zhu
on Mon, 2 May 2016 16:19:44 -0400 writes:
> Hi,
> I’m working on a Shiny app for statistical analysis. I ran into
this "maximal number of DLLs reached" issue recently because
Hello R Developers,
I posted some patches yesterday to your bug tracking system but I'm
not sure if I should have notified the mailing list as well. I haven't
gotten any responses yet.
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16603
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=1
Hi,
at the R prompt, is it possible to retrieve the last error (as in
condition object of class "error")?
I'm not asking for geterrmessage(), which only returns the error
message (as a character string). I'm basically looking for a
.Last.error or .Last.condition, analogously to .Last.value for v
> On May 4, 2016, at 12:41 PM, Henrik Bengtsson
> wrote:
>
> Hi,
>
> at the R prompt, is it possible to retrieve the last error (as in
> condition object of class "error")?
>
> I'm not asking for geterrmessage(), which only returns the error
> message (as a character string). I'm basically l
On Wed, May 4, 2016 at 1:27 PM, David Winsemius wrote:
>
>> On May 4, 2016, at 12:41 PM, Henrik Bengtsson
>> wrote:
>>
>> Hi,
>>
>> at the R prompt, is it possible to retrieve the last error (as in
>> condition object of class "error")?
>>
>> I'm not asking for geterrmessage(), which only return
On May 3, 2016, at 9:51 PM, Marius Hofert wrote:
> Dear expeRts,
>
> The following code leads to R being killed (under Mac OS X 10.11.4; R
> installed from source; also happened under a previous unstable
> version):
>
> m <- matrix(0, 10, 10)
>
> I expected an error that a vector of t
> Can you elaborate on "leads to R being killed"? You should tell to the killer
> not to do it again :).
Hi Simon!
Sure, but who do you tell it if you don't know the killer?
This is all the killer left me with, the 'crime scene' if you like :-)
> m <- matrix(0, 9, 10)
Killed: 9
My coll
On May 4, 2016, at 6:14 PM, Marius Hofert wrote:
>> Can you elaborate on "leads to R being killed"? You should tell to the
>> killer not to do it again :).
>
> Hi Simon!
>
> Sure, but who do you tell it if you don't know the killer?
> This is all the killer left me with, the 'crime scene' if
Hi Simon,
thanks for your quick reply.
1) ... so you can reproduce this?
2) Do you know a way how this can be 'foreseen'? We allocate larger
matrices in the copula package depending on the user's input
dimension. It would be good to tell her/him "Your dimension is quite
large. Be aware of killers
On May 4, 2016, at 9:00 PM, Marius Hofert wrote:
> Hi Simon,
>
> thanks for your quick reply.
>
> 1) ... so you can reproduce this?
Yes, I can on 10.11.4.
> 2) Do you know a way how this can be 'foreseen'? We allocate larger
> matrices in the copula package depending on the user's input
> d
Hi,
Interesting "feature" in 10.11.4. I wonder if the process is killed
before or after malloc() returns. If before, it seems very blunt:
"You're asking too much and I don't like it so I kill you now".
If after it doesn't look much better: "You're asking a lot and I
don't like it but I give it to
On May 4, 2016, at 9:49 PM, Hervé Pagès wrote:
> Hi,
>
> Interesting "feature" in 10.11.4. I wonder if the process is killed
> before or after malloc() returns. If before, it seems very blunt:
> "You're asking too much and I don't like it so I kill you now".
> If after it doesn't look much bett
Hi Simon,
... all interesting (but quite a bit above my head). I only read
'Linux' and want to throw in that this problem does not appear on
Linux (it seems). I talked about this with Martin Maechler and he
reported that the same example (on one of his machines; with NA_real_
instead of '0's in th
If you set the "digits17" control option in deparse, you get a lot of
unnecessary space in the representation of complex numbers.
> deparse(0 + 0i)
[1] "0+0i"
> deparse(0 + 0i, control = "digits17")
[1] "0 + 0i"
As far as I can tell, the logic for this comes from this piece of
/sr
17 matches
Mail list logo
