a PDF file yourself, then use the "as.is" feature of the
> R.rsp
> | >> | package.
> | >> For completeness, that approach also works directly with Sweave.
> Described in
> | >> a blog post by Mark van der
>
> Best,
> Uwe Ligges
>
>
>
> On 28.08.2023 00:37, John Harrold wrote:
> > Oh I'm sorry. It's the ruminate package.
> >
> > On Sun, Aug 27, 2023 at 2:22 PM Uwe Ligges
> > > <mailto:lig...@statistik.tu-dortmund.de>> wrote:
> >
> &g
Oh I'm sorry. It's the ruminate package.
On Sun, Aug 27, 2023 at 2:22 PM Uwe Ligges
wrote:
>
>
> On 27.08.2023 22:51, John Harrold wrote:
> > Howdy Folks,
> >
> > I submitted a package on Friday. I got the normal email where you have to
> > click on the lin
Howdy Folks,
I submitted a package on Friday. I got the normal email where you have to
click on the link to confirm. Then I got an email saying that the package
was uploaded. Normally after that I get an email saying the package was
auto-processed. That generally doesn't take very long (typically
ou can just do
>
> if (requireNamespace("", quietly=TRUE)) {
> # do the tests involving
> }
>
> Wasn't that enough?
>
> Best,
> Serguei.
>
>
> Le 18/07/2023 à 16:37, John Harrold a écrit :
> > Howdy Folks,
> >
> > I recent had a pack
Howdy Folks,
I recent had a package start failing because I wasn't checking properly in
my tests to make sure my suggested packages were installed before running
tests. I think this is something new running on CRAN where packages are
tested with only the packages specified as Imports in the
gPMX", verbose = FALSE) could be
> enough
>
> There's also an example that seems to be failing, I didn't understand
> the reason behind it but it might be related.
>
> Best,
>
> Lluís
>
>
> On Fri, 2 Jun 2023 at 02:49, John Harrold
> wrote:
> >
> >
Hello,
I recently got a "Dear Maintainer" email from Brian Ripley. It was
concerning the nlmixr2rpt package I maintain:
https://cran.r-project.org/web/checks/check_results_nlmixr2rpt.html
It looks like there is an error on r-release-linux-x86_64 that is causing
it. If I'm reading that correctly
Howdy Folks,
I got a message from CRAN today telling me that I have a strong reverse
dependency on the isoband package. But I'm not alone! It look like more
than 4700 other packages also have a strong dependency on this. Is there
some organized effort to deal with this?
Thanks
John
ere '(2)' is really much closer to the
> > >> "install time" you mention.
> > >>
> >
> > > I meant building the tarball, and assumed that was what Ivan was
> talking
> > > about as well.
> >
> > >
on-linear with data size? 27 seconds of user CPU is an awful lot
> of processing these days.
>
> Greg
>
> On Wed, 14 Sept 2022 at 13:21, John Harrold
> wrote:
>
>> Hello,
>>
>> I'm working on submitting a new package. I've created examples for each of
>> the fu
Hello,
I'm working on submitting a new package. I've created examples for each of
the functions. Most of these functions depend on an R object that uses
architecture-specific compiled code. To create that object can take between
10-20 seconds. The function that creates it will cache it in the
I don't have cigwin installed but from the command window, the terminal
that Git installs, RGui, and RStudio they all return "windows" for the
.Platform$OS.type for me.
On Thu, Sep 30, 2021 at 2:38 PM Duncan Murdoch
wrote:
> On 30/09/2021 5:21 p.m., Jeff Newmiller wrote:
> > What if you are on
I have a list of words, acronyms and initialisms that commonly get flagged
as misspelled words when I submit updates. I generally just put an
explanation for each one in the "optional comment" section of the
submission form. It's pretty simple and seems to work out well.
On Fri, Jul 16, 2021 at
To add another option. In the past when this has happened to me I've found
other packages that provide similar functionality.
I'm assuming that is.square just checks the number of columns == number of
rows? And the others can probably be implemented pretty easily.
On Wed, Jun 2, 2021 at 10:41 AM
of Computer Science
> University of Manitoba
> maxturgeon.ca
>
>
> ------
> *From:* R-package-devel on behalf
> of John Harrold
> *Sent:* September 15, 2019 11:31:38 AM
> *To:* Uwe Ligges
> *Cc:* r-package-devel@r-project.org
> *Subject:*
:
>
>
> On 15.09.2019 05:39, John Harrold wrote:
> > Thanks Uwe,
> >
> > Is there a way to find out on my end where this is happening?
>
> Yes, simply set the env var
> _R_CHECK_LIMIT_CORES_=true
> to reproduce.
>
> Best,
> Uwe
>
> >
> &g
Thanks Uwe,
Is there a way to find out on my end where this is happening?
Thanks
john
On Fri, Sep 13, 2019 at 10:51 PM Uwe Ligges
wrote:
>
>
> On 14.09.2019 03:33, John Harrold wrote:
> > Hello,
> >
> > I recently submitted a package for consideration in CR
Hello,
I recently submitted a package for consideration in CRAN. One of the
comments was:
Please ensure that you do not use more than 2 cores in your examples.
I do not believe my package does this. Is this a general comment for a
package that requires doParallel or was this triggered because
Howdy Folks,
I'm getting the following warning:
Found the following significant warnings:
Warning: replacing previous import ‘gdata::combine’ by
‘gridExtra::combine’ when loading
In the R scripts I'm using
#'@importFrom gridExtra grid.arrange
To only import the function I want, but I'm not
submission, clarifying that this is indeed
> a false positive.
>
> cheers
> Ben Bolker
>
> On 2019-08-19 6:13 p.m., John Harrold wrote:
> > Hello,
> >
> > I am attempting to submit my first package to CRAN. I believe I've
> > successfully gotten rid of al
Hello,
I am attempting to submit my first package to CRAN. I believe I've
successfully gotten rid of all the notes, but there is one that I'm unable
to eliminate. In the DESCRIPTION file in both the Title and Description
fields I use the term PKPD. This stands for Pharmacokinetics and
22 matches
Mail list logo
