[Rd] Implementing `sd` and `var` as generic functions

[Nicholas Tierney]

Hi everyone,

It seems that `sd` and `var` are currently not implemented as generic
functions. I was wondering if it is possible to request that they be
implemented, or if there is a proper process to go through doing that?

Apologies if this has already been discussed!

Cheers,

Nick

[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] 1954 from NA

[Nicholas Tierney]

Hi all,

When first hearing about ALTREP I've wondered how it might be able to be
used to store special missing value information - how can we learn more
about implementing ALTREP classes? The idea of carrying around a "meaning
of my NAs" vector, as Gabe said, would be very interesting!

I've done a bit on creating "special missing values", as done in SPSS, SAS,
and STATA, here:
http://naniar.njtierney.com/articles/special-missing-values.html  (Note
this approach requires carrying a duplicated dataframe of missing data
around with the data - which I argue makes it easier to reason with, at the
cost of storage. However this is just my approach, and there are others out
there).

Best,

Nick

On Tue, 25 May 2021 at 01:16, Adrian Dușa  wrote:

> On Mon, May 24, 2021 at 5:47 PM Gabriel Becker 
> wrote:
>
> > Hi Adrian,
> >
> > I had the same thought as Luke. It is possible that you can develop an
> > ALTREP that carries around the tagging information you're looking for in
> a
> > way that is more persistent (in some cases) than R-level attributes and
> > more hidden than additional user-visible columns.
> >
> > The downsides to this, of course, is that you'll in some sense be doing
> > the same "extra vector for each vector you want tagged NA-s within" under
> > the hood, and that only custom machinery you write will recognize things
> as
> > something other than bog-standard NAs/NaNs.  You'll also have some
> problems
> > with the fact that data in ALTREPs isn't currently modifiable without
> > losing ALTREPness. That said, ALTREPs are allowed to carry around
> arbitrary
> > persistent information with them, so from that perspective making an
> ALTREP
> > that carries around a "meaning of my NAs" vector of tags in its metadata
> > would be pretty straightforward.
> >
>
> Oh... now that is extremely interesting.
> It is the first time I came across the ALTREP concept, so I need to study
> the way it works before saying anything, but definitely something to
> consider.
>
> Thanks so much for the pointer,
> Adrian
>
> [[alternative HTML version deleted]]
>
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [R-pkg-devel] Error in winbuilder

[Nicholas Tierney]

Hi Uwe,

OK thank you for that, good to know! I imagine it might be a bit tricky to
know when, but do you have an idea of when submissions might return to
normal? Or should I be good to submit again soon?

Thanks again,

Nick

On Wed, 26 Aug 2020 at 23:06, Uwe Ligges 
wrote:

> Friends, thias looks like a hang in the CRAN incoming feasibility
> checks, hence may well be some web related issue as it seems it ran into
> the timeout there.
>
> Best,
> Uwe Ligges
>
> On 26.08.2020 14:57, Nicholas Tierney wrote:
> > Hi Michael,
> >
> > I do indeed have quite a few examples in the package, this hasn't been a
> > problem in the past, but I guess I could try reducing them down. Have you
> > had this problem before?
> >
> > Cheers,
> >
> > Nick
> >
> > On Wed, 26 Aug 2020 at 22:49, Michael Dewey 
> wrote:
> >
> >> Dear Nicholas
> >>
> >> Do you in fact have many examples in the package? Perhaps for some
> >> mysterious reason they take longer there than when you check at home.
> >>
> >> Michael
> >>
> >> On 25/08/2020 14:54, Nicholas Tierney wrote:
> >>> Hi Everyone,
> >>>
> >>> I have an error when submitting to Winbuilder for my R package, naniar
> >>> <https://github.com/njtierney/naniar>.
> >>>
> >>> When using `devtools::check_win_devel()` or
> >> `devtools::check_win_release()`
> >>> on naniar, I get the following logfile from winbuilder:
> >>>
> >>> ```
> >>> * using log directory 'd:/RCompile/CRANguest/R-release/naniar.Rcheck'
> >>> * using R version 4.0.2 (2020-06-22)
> >>> * using platform: x86_64-w64-mingw32 (64-bit)
> >>> * using session charset: ISO8859-1
> >>> * checking for file 'naniar/DESCRIPTION' ... OK
> >>> * checking extension type ... Package
> >>> * this is package 'naniar' version '0.5.3'
> >>> * package encoding: UTF-8
> >>> * checking CRAN incoming feasibility ... ERROR
> >>> Check process probably crashed or hung up for 20 minutes ... killed
> >>> Most likely this happened in the example checks (?),
> >>> if not, ignore the following last lines of example output:
> >>>
> >>>  End of example output (where/before crash/hang up occured ?)
> >>> 
> >>> ```
> >>>
> >>> (submission URL here: https://win-builder.r-project.org/77PYyM2kMri1/)
> >>>
> >>> I had previously thought this was a problem to do with CRAN being
> closed
> >>> last week, but apparently this is not the case, and it should have been
> >>> working. I cannot find any details on CRAN for this, but it passes
> build
> >> on
> >>> R HUB for windows, and it passes build with no warnings, errors, or
> notes
> >>> for me on Mac OSX, as well as on github actions (windows, macOS, and
> >>> ubuntu).
> >>>
> >>> Just wondering if anyone has thoughts on this? I have also cross
> >>> posted on Rstudio
> >>> community
> >>> <
> >>>
> >>
> https://community.rstudio.com/t/winbuilder-error-check-process-probably-crashed-or-hung-up-for-20-minutes-killed/77492
> >>>> ,
> >>> in case that is of interest.
> >>>
> >>> Thanks for your time, and apologies if I have missed something obvious.
> >>>
> >>> All the best,
> >>>
> >>> Nick
> >>>
> >>>[[alternative HTML version deleted]]
> >>>
> >>> __
> >>> R-package-devel@r-project.org mailing list
> >>> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >>>
> >>
> >> --
> >> Michael
> >> http://www.dewey.myzen.co.uk/home.html
> >>
> >
> >   [[alternative HTML version deleted]]
> >
> > __
> > R-package-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >
>

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Error in winbuilder

[Nicholas Tierney]

Hi Michael,

I do indeed have quite a few examples in the package, this hasn't been a
problem in the past, but I guess I could try reducing them down. Have you
had this problem before?

Cheers,

Nick

On Wed, 26 Aug 2020 at 22:49, Michael Dewey  wrote:

> Dear Nicholas
>
> Do you in fact have many examples in the package? Perhaps for some
> mysterious reason they take longer there than when you check at home.
>
> Michael
>
> On 25/08/2020 14:54, Nicholas Tierney wrote:
> > Hi Everyone,
> >
> > I have an error when submitting to Winbuilder for my R package, naniar
> > <https://github.com/njtierney/naniar>.
> >
> > When using `devtools::check_win_devel()` or
> `devtools::check_win_release()`
> > on naniar, I get the following logfile from winbuilder:
> >
> > ```
> > * using log directory 'd:/RCompile/CRANguest/R-release/naniar.Rcheck'
> > * using R version 4.0.2 (2020-06-22)
> > * using platform: x86_64-w64-mingw32 (64-bit)
> > * using session charset: ISO8859-1
> > * checking for file 'naniar/DESCRIPTION' ... OK
> > * checking extension type ... Package
> > * this is package 'naniar' version '0.5.3'
> > * package encoding: UTF-8
> > * checking CRAN incoming feasibility ... ERROR
> > Check process probably crashed or hung up for 20 minutes ... killed
> > Most likely this happened in the example checks (?),
> > if not, ignore the following last lines of example output:
> >
> >  End of example output (where/before crash/hang up occured ?)
> > 
> > ```
> >
> > (submission URL here: https://win-builder.r-project.org/77PYyM2kMri1/)
> >
> > I had previously thought this was a problem to do with CRAN being closed
> > last week, but apparently this is not the case, and it should have been
> > working. I cannot find any details on CRAN for this, but it passes build
> on
> > R HUB for windows, and it passes build with no warnings, errors, or notes
> > for me on Mac OSX, as well as on github actions (windows, macOS, and
> > ubuntu).
> >
> > Just wondering if anyone has thoughts on this? I have also cross
> > posted on Rstudio
> > community
> > <
> >
> https://community.rstudio.com/t/winbuilder-error-check-process-probably-crashed-or-hung-up-for-20-minutes-killed/77492
> >> ,
> > in case that is of interest.
> >
> > Thanks for your time, and apologies if I have missed something obvious.
> >
> > All the best,
> >
> > Nick
> >
> >   [[alternative HTML version deleted]]
> >
> > __
> > R-package-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >
>
> --
> Michael
> http://www.dewey.myzen.co.uk/home.html
>

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] Error in winbuilder

[Nicholas Tierney]

Hi Everyone,

I have an error when submitting to Winbuilder for my R package, naniar
.

When using `devtools::check_win_devel()` or `devtools::check_win_release()`
on naniar, I get the following logfile from winbuilder:

```
* using log directory 'd:/RCompile/CRANguest/R-release/naniar.Rcheck'
* using R version 4.0.2 (2020-06-22)
* using platform: x86_64-w64-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking for file 'naniar/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'naniar' version '0.5.3'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... ERROR
Check process probably crashed or hung up for 20 minutes ... killed
Most likely this happened in the example checks (?),
if not, ignore the following last lines of example output:

 End of example output (where/before crash/hang up occured ?)

```

(submission URL here: https://win-builder.r-project.org/77PYyM2kMri1/)

I had previously thought this was a problem to do with CRAN being closed
last week, but apparently this is not the case, and it should have been
working. I cannot find any details on CRAN for this, but it passes build on
R HUB for windows, and it passes build with no warnings, errors, or notes
for me on Mac OSX, as well as on github actions (windows, macOS, and
ubuntu).

Just wondering if anyone has thoughts on this? I have also cross
posted on Rstudio
community
<
https://community.rstudio.com/t/winbuilder-error-check-process-probably-crashed-or-hung-up-for-20-minutes-killed/77492
>,
in case that is of interest.

Thanks for your time, and apologies if I have missed something obvious.

All the best,

Nick

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel