Re: [R-pkg-devel] Question about examples/tests run-time

[Lluís Revilla]

Dear Mallory,

It would help a little bit if we know the package and we can check the
examples and code.
Perhaps it can help this little explanation of when to use donttest,
dontrun and other options:
https://contributor.r-project.org/cran-cookbook/general_issues.html#structuring-of-examples
If it is still too long I would leave the representative example for a
vignette or demo (or an article if you use pkgdown) and show how to use the
different parameters of your functions in the examples.

Best,

On Wed, 9 Oct 2024 at 23:04, Mallory Flynn 
wrote:

> Hello,
>
> I am hoping this is the correct way to pose a question about my
> submission, which I can’t seem to fix 2 NOTES for.  They are related to run
> time:
> Flavor: r-devel-windows-x86_64
> Check: examples, Result: NOTE
> Examples with CPU (user + system) or elapsed time > 10s
>user system elapsed
> countTree 17.66   0.13   17.78
> estTree   17.52   0.02   17.54
> wmmTree   15.70   0.02   15.72
>
> Flavor: r-devel-linux-x86_64-debian-gcc
> Check: examples, Result: NOTE
> Examples with CPU (user + system) or elapsed time > 5s
> user system elapsed
> countTree 14.218  0.077  14.401
> wmmTree   14.049  0.028  14.086
> estTree   14.046  0.012  14.066
>
> The package enables easy implementation of a sampling method for
> population size estimation on a highly correlated tree - since it’s
> sequentially sampled, it’s expected to run long compared to other
> functionality, even on smaller examples.
> I have added many layers to try to shorten examples and tests, including
> “donttest”, “dontrun”, “if (interactive())”, and reducing toy examples to
> what I believe is the smallest they can be to still demonstrate utility.  I
> also included the “skip_on_cran()” function in tests which run longer.
>
> Does anyone else have any ideas on how I can eliminate these notes?
>
> Any help is very much appreciated!!
> Thank you!
> __
> 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

[R-pkg-devel] Help with 2 NOTES

[Jaime Salvador]

How I can solve this NOTES:


* checking CRAN incoming feasibility ... [3s/5s] NOTE
Maintainer: ‘Jaime Salvador <
jaime.salva...@ideasybits.com>’

New submission

Possibly misspelled words in DESCRIPTION:
  DICX (12:67)
  RXDB (12:59)
  Redatam (2:34, 12:40)



* checking for detritus in the temp directory ... NOTE

Found the following files/directories:
  ‘redatam’



Thanks

-
Jaime Salvador
| Ideas&Bits
| mobile: +593 0987285748
| email: jaime.salva...@ideasybits.com
| site: 
www.ideasybits.com



[[alternative HTML version deleted]]

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

[R-pkg-devel] Question about examples/tests run-time

[Mallory Flynn]

Hello,

I am hoping this is the correct way to pose a question about my submission, 
which I can’t seem to fix 2 NOTES for.  They are related to run time:
Flavor: r-devel-windows-x86_64
Check: examples, Result: NOTE
Examples with CPU (user + system) or elapsed time > 10s
   user system elapsed
countTree 17.66   0.13   17.78
estTree   17.52   0.02   17.54
wmmTree   15.70   0.02   15.72

Flavor: r-devel-linux-x86_64-debian-gcc
Check: examples, Result: NOTE
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
countTree 14.218  0.077  14.401
wmmTree   14.049  0.028  14.086
estTree   14.046  0.012  14.066

The package enables easy implementation of a sampling method for population 
size estimation on a highly correlated tree - since it’s sequentially sampled, 
it’s expected to run long compared to other functionality, even on smaller 
examples. 
I have added many layers to try to shorten examples and tests, including 
“donttest”, “dontrun”, “if (interactive())”, and reducing toy examples to what 
I believe is the smallest they can be to still demonstrate utility.  I also 
included the “skip_on_cran()” function in tests which run longer.

Does anyone else have any ideas on how I can eliminate these notes?

Any help is very much appreciated!!
Thank you!
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel