Biostrings 2.70.2

This document presents some basic and simple tools for dealing with the
oligonucleotide microarray reporter sequence information in the Bioconductor
*probe* packages. This information is used, for example, in the
*gcrma* package.

*Probe* packages are a convenient way for distributing and storing the probe
sequences (and related information) of a given chip.

As an example, the package *hgu95av2probe* provides microarray
reporter sequences for Affymetrix’ *HgU95a version 2* genechip, and for almost
all major Affymetrix genechips, the corresponding packages can be downloaded
from the Bioconductor website. If you have the reporter sequence information of
a particular chip, you can also create such a package yourself. This is
described in the makeProbePackage vignette of the *AnnotationForge*
package.

This document assumes some basic familiarity with R and with the design of the
*AffyBatch* class in the *affy* package, Bioconductor’s basic
container for Affymetrix genechip data.

First, let us load the *Biostrings* package and some other packages
we will use.

```
library(Biostrings)
library(hgu95av2probe)
library(hgu95av2cdf)
```

Help for the probe sequence data packages can be accessed through

`?hgu95av2probe`

One of the issues that you have to deal with is that the *probe* packages do not
provide the reporter sequences of all the features present in an *AffyBatch*.
Some sequences are missing, some are implied; in particular, the data structure
in the *probe* packages does not explicitly contain the sequences of the
mismatch probes, since they are implied by the perfect match probes. Also, some
other features, typically harboring control probes or empty, do not have
sequences. This is the choice that Affymetrix made when they made files with
probe sequences available, and we followed it.

Practically, this means that the vector of probe sequences in a *probe* package
does not align 1:1 with the rows of the corresponding *AffyBatch*; you need to
keep track of this mapping, and some tools for this are provided and explained
below (see Section 2.2). It also means that some functions from the
*affy* package, such as `pm`

, cannot be used when the sequences of
the probes corresponding to their result are needed; since `pm`

reports the
intensities, but not the identity of the probes it has selected, yet the latter
would be needed to retrieve their sequences.

Let us look at some basic operations on the sequences.

DNA sequences can be reversed and/or complemented with the `reverse`

,
`complement`

and `reverseComplement`

functions.

`?reverseComplement`

```
pm <- DNAStringSet(hgu95av2probe)
dict <- pm[3801:4000]
pdict <- PDict(dict)
m <- vcountPDict(pdict, pm)
dim(m)
```

`## [1] 200 201800`

`table(rowSums(m))`

```
##
## 1 2 3
## 179 15 6
```

`which(rowSums(m) == 3)`

`## [1] 77 79 80 81 82 83`

```
ii <- which(m[77, ] != 0)
pm[ii]
```

```
## DNAStringSet object of length 3:
## width seq
## [1] 25 TCGTCATCAGGTGCATAGCAAGTGA
## [2] 25 TCGTCATCAGGTGCATAGCAAGTGA
## [3] 25 TCGTCATCAGGTGCATAGCAAGTGA
```

The base content (number of occurrence of each character) of the sequences can
be computed with the function `alphabetFrequency`

.

```
bcpm <- alphabetFrequency(pm, baseOnly=TRUE)
head(bcpm)
```

```
## A C G T other
## [1,] 1 10 6 8 0
## [2,] 5 5 5 10 0
## [3,] 6 4 3 12 0
## [4,] 4 7 8 6 0
## [5,] 4 5 8 8 0
## [6,] 2 7 6 10 0
```

`alphabetFrequency(pm, baseOnly=TRUE, collapse=TRUE)`

```
## A C G T other
## 1250858 1235532 1186629 1371981 0
```

```
nc = hgu95av2dim$NCOL
nc
```

`## [1] 640`

```
nr = hgu95av2dim$NROW
nr
```

`## [1] 640`

Each column of an *AffyBatch* corresponds to an array, each row to a certain
probe on the arrays. The probes are stored in a way that is related to their
geometrical position on the array. For example, the *hgu95av2* array is
geometrically arranged into 640 columns and 640 rows. We call the column
and row indices the `x`

- and `y`

-coordinates, respectively. This results in
640 ⨉ 640 = 409600 probes of the *AffyBatch*;
we also call them indices. To convert between `x`

-and `y`

-coordinates and
indices, you can use the functions `xy2indices`

and `indices2xy`

from the
*affy* package.

The sequence data in the *probe* packages is addressed by their `x`

and
`y`

-coordinates. Let us construct a vector `abseq`

that aligns with the indices
of an *hgu95av2* *AffyBatch* and fill in the sequences:

```
library(affy)
abseq = rep(as.character(NA), nc*nr)
ipm = with(hgu95av2probe, xy2indices(x, y, nc=nc))
any(duplicated(ipm)) # just a sanity check
```

`## [1] FALSE`

```
abseq[ipm] = hgu95av2probe$sequence
table(is.na(abseq))
```

```
##
## FALSE TRUE
## 201800 207800
```

The mismatch sequences are not explicitly stored in the probe packages. They are
implied by the match sequences, by flipping the middle base. This can be done
with the `pm2mm`

function defined below. For Affymetrix GeneChips the length of
the probe sequences is 25, and since we start counting at 1, the middle position
is 13.

```
mm <- pm
subseq(mm, start=13, width=1) <- complement(subseq(mm, start=13, width=1))
cat(as.character(pm[[1]]), as.character(mm[[1]]), sep="\n")
```

```
## TGGCTCCTGCTGAGGTCCCCTTTCC
## TGGCTCCTGCTGTGGTCCCCTTTCC
```

We compute `imm`

, the indices of the mismatch probes, by noting that each
mismatch has the same `x`

-coordinate as its associated perfect match, while its
`y`

-coordinate is increased by 1.

```
imm = with(hgu95av2probe, xy2indices(x, y+1, nc=nc))
intersect(ipm, imm) # just a sanity check
```

`## numeric(0)`

```
abseq[imm] = as.character(mm)
table(is.na(abseq))
```

```
##
## FALSE TRUE
## 403600 6000
```

See Figures 1-3 for some applications of the probe sequence information to preprocessing and data quality related plots.