Note that I sent this to r-devel, yesterday.
However, it didn't appear on the mailing list.
So, I'm resending it.
Today, I plotted the following:
> filled.contour (,,z, color.palette=terrain.colors)
It looked OK, in R.
However, when I created a PDF document, the plot (and other similar plots)
Dear colleagues,
I submitted a new package on Saturday, 9 March 2019.
Approx. 48 hours ago, i.e. on Wednesday, 13 March 2019, my package was moved to
the subfolder "pending".
I am worried, because I did not receive any email from CRAN concerning why my
package was "pending" and what I needed
Hi Erik,
I think the problem was introduced in a contributed patch applied to
VariantAnnotation in devel. I've reverted the patch and expect
VariantAnnotation (and downstream packages) to clear up on Windows with
tomorrow's builds.
Valerie
On Thu, Mar 7, 2019 at 4:10 AM Erik Fasterius
wrote:
>
Hi Gordon,
My understanding is that adding .BBSoptions to the .Rbuildignore file
will tell 'R CMD build' to not include the file in the resulting source
tarball, which is good (cleaner tarball).
And since the build system reads the .BBSoptions file from the package
source tree, not from the
Hello Maintainers,
Just to clarify, these packages were tested on a Docker image
“bioconductor_full” which aims to capture all the system dependencies.
Other than CATALYST which is actually failing on both RELEASE_3_8 and devel
build systems because of errors, the remaining 3 packages are
Please refer to the documentation (?stop, ?recover, ?dump.frames). In
non-interactive use, recover() works as dump.frames(). dump.frames() is
documented not to quit R, and the examples show how to quit the R
session with a given status automatically after dump.frames(). So in
line with the
My point was that, in a table, the row and columns usually have a well-defined
order. If you convert the table to data frame form, typically in order to fit a
Poisson GLM, you do want to preserve that order, and not have the levels
converted to a locale-dependent alphabetical order in your
I have to disagree with both Peter and Martin on this.
The underneath issue is that the automatic conversion of characters to factors
by the
data.frame functions was the single most egregious design blunder in the
Statistical
Models in S book, and we are still living with it. The
This page is more accurate:
http://bioconductor.org/developers/package-guidelines/#vignettes
but we should update the /help/package-vignettes/ as well thank you for
pointing to this.
Keep in mind that the github repo is not the canonical location for
Bioconductor package. On Bioconductor I
Peter,
Thanks for the response. I have no wish to prolong this and have no axe to
grind. I’m sure you were delighted to see another stringsAsFactors issue.
Perhaps we talking about the conflation of two steps: the first is the language
‘pure' conversion of the table to a data.frame with the
10 matches
Mail list logo
