Re: [Bioc-devel] ERROR: More than one VignetteEngine specified.

Dear Lluis, Thank you for looking into it. I deleted `it,` and it and the error went away. Best, Witek On 19/11/2021 16:36, Lluís Revilla wrote: Hi Witek, Probably it is a false positive, caused by a commented VignetteEngine on https://github.com/protViz/prozor/blob/master/vignettes/Target

Re: [Bioc-devel] EXTERNAL: LazyData: false and accessing data in the YAML section of an Rmd document

Dear Andrew, Thanks for your suggestion. Loading the data explicitly in the markdown instead of the YAML section - appeals to me. It is desirable to show the code in the vignette if the vignette loads it. However, I would like not to display the code if I pass the data using the params argu

[Bioc-devel] WARNING: Add non-empty \value sections to the following

Hello, BiocCheck produces the following warning for function with no return value. WARNING: Add non-empty \value sections to the following man pages: x.Rd, y.Rd, z.Rd However, the functions x, y, and z do not return a value since these are functions which, e.g., plot to grDevices, or write to

[Bioc-devel] Fwd: WARNING: Add non-empty \value sections to the following

Dear BioConductor developers, Two windows users of a package that I'm developing (soon to be submitted to BioC) have encountered the same error : ``` Error: BiocParallel errors � element index: 1, 2, 3 � first error: invalid length of row names ```

Re: [Bioc-devel] Fwd: WARNING: Add non-empty \value sections to the following

Linux and macOS use MulticoreParam() by default, and the 'workers' inherit the environment (e.g., loaded packages) of the 'manager'. Windows doesn't support this mode, and instead uses SnowParam() by default; likely you'll be able to reproduce the error on your system by using SnowParam(), perha

[Bioc-devel] S4 Method Slow Execution if Signature Has Multiple Class Unions

Good day, I created two constructor methods for a generic function. One is for the default empty constructor and the other is a constructor when any one or more parameters is specified by the user. The method signatures are: 1. c("missing", "missing", "missing", "missing", "missing", "missing",