Skip to content

[Bioc-devel] Cannot reproduce Bioc build server errors for annotatr package

3 messages · Martin Morgan, Raymond Cavalcante

#
Hello all,

I?m getting some CHECK errors in the examples and tests for the annotatr package (http://bioconductor.org/checkResults/devel/bioc-LATEST/annotatr/ <http://bioconductor.org/checkResults/devel/bioc-LATEST/annotatr/>) that I cannot reproduce using the bioconductor/devel_core2 Docker image + most up-to-date packages. I think the issue is coming from rtracklayer while reading in a BED (or BED-like) file that has '.' in the strand column instead of '+', '-', or '*'.

Here is the error on the build system for all three platforms:
Below is my sessionInfo() for the Docker image based on the https://hub.docker.com/r/bioconductor/devel_core2/ <https://hub.docker.com/r/bioconductor/devel_core2/> image. I suppose I could change all of my example data to use '*' for the strand, but many peak callers (macs2 being one of the most popular) use the '.' convention for no strand in their BED output, and I think rtracklayer should respect this.

Thanks, Raymond

  
  
3 days later
#
On 10/23/2017 09:22 AM, Raymond Cavalcante wrote:
I'm not able to reproduce this off the build system either, but the 
problem is the space after the strand '- ' instead of '-' in the second 
line,

 > r_file = system.file('extdata', 'test_read_multiple_data_nohead.bed', 
package='annotatr')
 > readLines(r_file)
[1] "chr1\t10800\t10900\tA\t87\t+\t10e-4\t100\t13\tY"
[2] "chr1\t11000\t11100\tA\t45\t- \t1e-6\t100\t55\tN"
[3] "chr1\t27800\t28800\tA\t34\t-\t0.04\t41\t7\tY"
[4] "chr1\t29000\t29300\tB\t62\t+\t0.001\t95\t33\tY"

Maybe Michael has some insight...?

Martin
This email message may contain legally privileged and/or...{{dropped:2}}
#
Hi Martin,

A ha! Thank you for pointing that out. Not sure how that space got in there, but I?ll remove it and hopefully it?ll clear the error. Odd about the reproducibility though?

Thanks again,
Raymond