Does the old package give incorrect results? Or does it just give slower
results? What makes the new one better?
Unless the old one is actually wrong, as a user, I would be unhappy with it
being replaced by a shell. I have this obsession with reproducibility. So,
if you force me to change to the n
Thanks. I was already using a monospace font when I referred specifically
to the package.
On Mon, Dec 30, 2024, 12:07 PM Dirk Eddelbuettel wrote:
>
> On 30 December 2024 at 11:24, Kevin Coombes wrote:
> | Thanks; I suspected as much. I will try changing the name of the
> algorithm
Thanks; I suspected as much. I will try changing the name of the algorithm
(in the manuscript) to uppercase, and leave the package name alone.
On Mon, Dec 30, 2024, 10:59 AM Duncan Murdoch
wrote:
> On 2024-12-30 10:36 a.m., Kevin R. Coombes wrote:
> > Hi,
> >
> > I currently have a package on CR
I have been using R-Forge for many years for package development. And I
have been using GitLab for other projects almost as long.
However, over the past few months, the R-Forge support seems to be
decaying, and I now have several projects that won't currently build there
because of various items t
Hi,
I've been building a package and hit a NAMESPACE issue that took a while
to resolve.
My package implements a (new) generic function, and the method for a
package in the class calls the "smoothScatter" function from the
"graphics" package. I could build and install the package successfull
lt; "3.6.0"
> could solve the issue of an inconsistent test result and is descriptive.
>
> Best regards,
>
> Sebastian
>
>
> Am 06.12.18 um 16:59 schrieb Kevin Coombes:
>> Hi,
>>
>> A package I recently submitted to CRAN includes an S4 class
Hi,
A package I recently submitted to CRAN includes an S4 class that defines a
method to coerce from that class to a numeric vector, basically through
> setAs("myClass", "numeric", function(from) from@psi)
Being perhaps overly compulsive about trying to test everything while
documenting behavi
those get through? Did they make sense?
>
> On Thu, May 17, 2018 at 3:30 PM, Kevin Coombes
> wrote:
> > Yes; I'm pretty sure that it is exactly the repeated eigenvalues that are
> > the issue. The matrices I am using are all nonsingular, and the various
> > algorithm
] 0.000 0.00e+00 0.00e+00 -1 0.0
> [5,] 0.8660254 4.464109e-17 -1.112441e-160 0.5
>
>
>
>
>
> Bill Dunlap
> TIBCO Software
> wdunlap tibco.com
>
> On Thu, May 17, 2018 at 10:14 AM, Martin Maechler <
> maech...@stat.math.ethz.ch> wrote:
>
Hi,
I wrote and maintain the Thresher package. It includes code to do
simulations. In the "tests" directory of the package, I do some simple
simulations and run the main algorithm, then write out summaries of the
results
The initial submission of the package to CRAN was delayed because the
"Rout.
Hi,
I'm going to start by summarizing the suggestions (for where to put the
script) that have been presented so far:
[1] in the /demo directory
[2] in /inst/SOMETHING, where Dirk lists four possible values for SOMETHING
[3] in /R , but hidden using .Rbuildignore
[4] in the Example section of a
Hi,
I'm currently developing an R package that includes a small data set
along with the functions that I want to export. I have an R script that
generates the data set; the computation time is long (well, relative to
the size of the data set). So, my plan is to run the script and save()
the d
s added ...
Ben Bolker
On 15-06-18 08:45 AM, Kevin Coombes wrote:
Hello,
In putting together my latest package, I'm getting the following
warning from "R CMD check --as-cran"
* checking package subdirectories ... WARNING Subdirectory
'inst/doc' contains invalid fil
Hello,
In putting together my latest package, I'm getting the following warning
from "R CMD check --as-cran"
* checking package subdirectories ... WARNING
Subdirectory 'inst/doc' contains invalid file names:
'02oneGeneSims.Rnw' '02oneGeneSims.pdf'
Please remove or rename the files.
See secti
Hi,
When I run "R CMD check --as-cran" on my packages in R 3.2.0, I now get
a new series of NOTE's telling me that (1) the Description field in the
DESCRIPTION should file should not start with "This package" or with the
package name, and (2) the Title field in the DESCRIPTION file should be
15 matches
Mail list logo
