Re: [Rd] How to address the following: CRAN packages not using Suggests conditionally

2018-01-22 Thread Iñaki Úcar
Re-sending, since I forgot to include the list, sorry. I'm including r-package-devel too this time, as it seems more appropriate for this list. El 22 ene. 2018 10:11, "Iñaki Úcar" escribió: > > > El 22 ene. 2018 8:12, "Ulrich Bodenhofer" > escribió: > > Dear colleagues, dear members of the R C

Re: [Rd] How to address the following: CRAN packages not using Suggests conditionally

2018-01-22 Thread Ulrich Bodenhofer
Thanks a lot, Iñaki, this is a perfect solution! I already implemented it and it works great. I'll wait for 2 more days before I submit the revised package to CRAN - in order to give others to comment on it. Best regards, Ulrich On 01/22/2018 10:16 AM, Iñaki Úcar wrote: Re-sending, since I fo

[Rd] Better error message in loadNamespace

2018-01-22 Thread Thomas Lin Pedersen
Hi I’ve just spend a bit of time debugging an error arising in `loadNamespace`. The bottom line is that the `vI` object is assigned within an `if` block but expected to exist for all of the remaining code. In some cases where the package library has been corrupted or when it resides on a networ

Re: [Rd] How to address the following: CRAN packages not using Suggests conditionally

2018-01-22 Thread Martin Morgan
On 01/22/2018 08:40 AM, Ulrich Bodenhofer wrote: Thanks a lot, Iñaki, this is a perfect solution! I already implemented it and it works great. I'll wait for 2 more days before I submit the revised package to CRAN - in order to give others to comment on it. It's very easy for 'pictures of code'

Re: [Rd] Better error message in loadNamespace

2018-01-22 Thread Martin Maechler
> Thomas Lin Pedersen > on Mon, 22 Jan 2018 14:32:27 +0100 writes: > Hi I’ve just spend a bit of time debugging an error > arising in `loadNamespace`. The bottom line is that the > `vI` object is assigned within an `if` block but expected > to exist for all of the rema

Re: [Rd] Better error message in loadNamespace

2018-01-22 Thread Thomas Lin Pedersen
> On 22 Jan 2018, at 16.21, Martin Maechler wrote: > >> Thomas Lin Pedersen mailto:thomas...@gmail.com>> >>on Mon, 22 Jan 2018 14:32:27 +0100 writes: > >> Hi I’ve just spend a bit of time debugging an error >> arising in `loadNamespace`. The bottom line is that the >> `vI` object i

[Rd] Inconsistent rank in qr()

2018-01-22 Thread Serguei Sokol
Hi, I have noticed different rank values calculated by qr() depending on LAPACK parameter. When it is FALSE (default) a true rank is estimated and returned. Unfortunately, when LAPACK is set to TRUE, the min(nrow(A), ncol(A)) is returned which is only occasionally a true rank. Would not it be m

Re: [Rd] Inconsistent rank in qr()

2018-01-22 Thread Keith O'Hara
This behavior is noted in the qr documentation, no? rank - the rank of x as computed by the decomposition(*): always full rank in the LAPACK case. > On Jan 22, 2018, at 11:21 AM, Serguei Sokol wrote: > > Hi, > > I have noticed different rank values calculated by qr() depending on > LAPACK p

Re: [Rd] Inconsistent rank in qr()

2018-01-22 Thread Serguei Sokol
Le 22/01/2018 à 17:40, Keith O'Hara a écrit : This behavior is noted in the qr documentation, no? rank - the rank of x as computed by the decomposition(*): always full rank in the LAPACK case. For a me a "full rank matrix" is a matrix the rank of which is indeed min(nrow(A), ncol(A)) but here

Re: [Rd] as.character(list(NA))

2018-01-22 Thread Hervé Pagès
On 01/20/2018 08:24 AM, William Dunlap via R-devel wrote: I believe that for a list as.character() applies deparse() to each element of the list. deparse() does not preserve NA-ness, as it is intended to make text that the parser can read. str(as.character(list(Na=NA, LglVec=c(TRUE,NA), Func

Re: [Rd] as.character(list(NA))

2018-01-22 Thread Robert McGehee
Also perhaps a surprise that the behavior depends on the mode of the NA. > is.na(as.character(list(NA_real_))) [1] FALSE > is.na(as.character(list(NA_character_))) [1] TRUE Does this mean deparse() preserves NA-ness for NA_character_ but not NA_real_? -Original Message- From: R-devel [

Re: [Rd] as.character(list(NA))

2018-01-22 Thread William Dunlap via R-devel
I tend to avoid using as. functions on lists, since they act oddly in several ways. E.g, if the list "L" consists entirely of scalar elements then as.numeric(L) acts like as.numeric(unlist(L)) but if any element is not a scalar there is an error. as.character() does not seem to make a distinction

Re: [Rd] as.character(list(NA))

2018-01-22 Thread Hervé Pagès
On 01/22/2018 01:02 PM, William Dunlap wrote: I tend to avoid using as. functions on lists, since they act oddly in several ways. E.g, if the list "L" consists entirely of scalar elements then as.numeric(L) acts like as.numeric(unlist(L)) but if any element is not a scalar there is an error.

Re: [Rd] Inconsistent rank in qr()

2018-01-22 Thread Keith O'Hara
I agree the result is a little confusing, but the behavior is in line with the documentation and so not ‘unexpected’ as such... I don’t think this is a matter of semantics, more of a ‘return the rank when we have it for free’ situation—when A is real-valued, qr(A,LAPACK=false) calls a modified

Re: [Rd] Inconsistent rank in qr()

2018-01-22 Thread Martin Maechler
> Serguei Sokol > on Mon, 22 Jan 2018 17:57:47 +0100 writes: > Le 22/01/2018 à 17:40, Keith O'Hara a écrit : >> This behavior is noted in the qr documentation, no? >> >> rank - the rank of x as computed by the decomposition(*): always full rank in the LAPACK case.