similar to: Strange, most probably unjustified, codoc mismatch for S4 method with one argument plus '...'

Hi, I just figured out that I accidentally posted my message in HTML, so I am retrying in plain text only. Sorry. I am currently extending one of our CRAN packages and ran into an unexpected problem when checking the source package. I got some warnings in the step "* checking for code/documentation mismatches". I double checked everything and did not see anything that would

Dear colleagues, This is to inform you that Version 1.3.0 of the R package apcluster has been released on CRAN yesterday. We did a major extension and overhaul of the package. Most importantly, we added Leveraged Affinity Propagation in fulfillment of multiple users requests. It should now be much easier to cluster large data sets. Apart from this extension, the interfaces to apcluster() and

[cross-posted to R-devel and bioc-devel] Hi, I am trying to implement a 'sort' method in one of the CRAN packages I am maintaining ('apcluster'). I started with using setMethod("sort", ...) in my package, which worked fine. Since many users of my package are from the bioinformatics field, I want to ensure that my package works smoothly with Bioconductor. The problem

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 forgot to include the list, sorry. I'm including > r-package-devel too this time, as it

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' (unevaluated code chunks in vignettes) to drift from the actual

Dear colleagues, This is to inform you that Version 1.3.1 of the R package apcluster has been released on CRAN. We did a major improvement of heatmap and dendrogram plotting, as well as several minor improvements of the package. For more details, see the following URLs: http://www.bioinf.jku.at/software/apcluster/ http://cran.r-project.org/web/packages/apcluster/index.html Best regards,

Dear colleagues, This is to inform you that I will be giving a webinar on the apcluster package on Thursday, June 13, 2013, 7:00pm CEST (10:00am PDT). The outline of the one-hour webinar is as follows: - Introduction to affinity propagation (AP) clustering - The apcluster package, its algorithms, and visualization tools - Live apcluster demonstration - Question and Answer period To register

That might be worth thinking about generally, but it would still be nice to have the base generics pre-defined, so that people are not copy and pasting the definitions everywhere, hoping that they stay consistent. On Wed, Mar 26, 2014 at 6:13 AM, Gabriel Becker <gmbecker@ucdavis.edu>wrote: > Perhaps a patch to R such that generics don't clobber each-other's method > tables

On 03/27/2014 02:13 AM, Ulrich Bodenhofer wrote: > I fully agree, Michael, that this would be a great thing to have! I have > often wondered why R and the standard packages are still sticking so > much to the old-style S3 flavor though S4 is part of standard R. I > acknowledge that backward compatibility is important, but, as far as I > got it, redefining a function or S3 generic as

I fully agree, Michael, that this would be a great thing to have! I have often wondered why R and the standard packages are still sticking so much to the old-style S3 flavor though S4 is part of standard R. I acknowledge that backward compatibility is important, but, as far as I got it, redefining a function or S3 generic as an S4 generic should not harm existing functionality (if done

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" <i.ucar86 at gmail.com> escribi?: > > > El 22 ene. 2018 8:12, "Ulrich Bodenhofer" <bodenhofer at bioinf.jku.at> > escribi?: > > Dear colleagues, dear members of

Dear colleagues, dear members of the R Core Team, This was an issue raised by Prof. Brian Ripley and sent privately to all developers of CRAN packages that suggest Bioconductor packages (see original message below). As mentioned in my message enclosed below, it was easy for me to fix the error in examples (new version not submitted to CRAN yet), but it might turn into a major effort for the

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

Hi, Doing 'R CMD check diveMove' is now throwing this message: Data codoc mismatches from documentation object 'sealLocs': Variables in data frame 'sealLocs' Code: id.time.class.lon.lat Docs: class id lat lon time with: R> sessionInfo() R version 2.10.1 (2009-12-14) x86_64-pc-linux-gnu locale: [1] LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=C

Dear Person That Posted This Email, Please be aware that calls for papers are only on-topic for this email list if they are specifically about LLVM. For example, a call for a workshop on LLVM in Scientific Computing would be on topic whereas a general compiler call for papers (like the one below) is not. That said, I hope you receive many strong submissions. Your conference looks

------------------------------------------------------------------------------------------------ CALL FOR PAPERS 15th International Conference on Managed Languages & Runtimes (ManLang'18) September 10-14, 2018, Linz, Austria http://ssw.jku.at/manlang18/ ------------------------------------------------------------------------------------------------ ManLang (formerly PPPJ) is a

Hi, I am using R on Ubuntu 12.10 (64bit). This morning, Ubuntu's software updater automatically installed updates to R's base system (version 2.15.3; via the CRAN PPA). Now R does not work anymore. Here is what I get when I simply enter "R" on the shell prompt: bodenhof FUKUOKA~>R cannot find system Renviron Error : .onLoad failed in loadNamespace() for 'utils',

On Tue, Oct 15, 2013 at 5:59 PM, David Blaikie <dblaikie at gmail.com> wrote: > > In beginModule, we construct the CUs, but not all the DIEs that belong >>>> to the CU. >>>> In endFunction, we started to construct the scope DIEs. So in some >>>> sense, we are adding things to prior CUs. >>>> >>>> Looking at void

On Tue, Oct 15, 2013 at 5:22 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Tue, Oct 15, 2013 at 4:59 PM, Manman Ren <manman.ren at gmail.com> wrote: > >> >> >> >> On Tue, Oct 15, 2013 at 2:24 PM, David Blaikie <dblaikie at gmail.com>wrote: >> >>> >>> >>> >>> On Tue, Oct 15, 2013 at

> In beginModule, we construct the CUs, but not all the DIEs that belong to >>> the CU. >>> In endFunction, we started to construct the scope DIEs. So in some >>> sense, we are adding things to prior CUs. >>> >>> Looking at void CompileUnit::addDIEEntry(DIE *Die, uint16_t Attribute, >>> DIE *Entry), we can possibly have 3 CUs, this CU,