Dear colleagues.
As most of you might know, CAP (as
originally described by Anderson & Willis 2003*) is a discriminant
analysis (or Canonical Correlation Analyses) on PCoA space. I am
referring to the discriminant option here**.
I have
found that the CAP menu in the Primer software (by Marti Anderson) and
the function CAPdiscrim in BiodiversityR (by Roeland Kindt) produce
different results in both 'best m' and classification rates, though they
result in the same PCoA space (identical multivariate representations,
different scales of PCoA axes) and identical Pillar trace statistic.
Using the dune dataset from BiodiversityR, m = 9 in BiodiversityR versus
m = 6 in Primer, while at any given m both platforms differ in
classification rates - the mismatch persists when I have done the same
with a range of my own datasets.
I wonder whether you
might have encountered this problem and figure out where the solution
lies. I have discussed the problem with Roeland but we could not find
out why this is happening.
Many thanks in advance for your thoughts.
Salva
*
Anderson, M.J., and Willis, T.J. (2003). Canonical analysis of
principal coordinates: A useful method of constrained ordination for
ecology. Ecology 84, 511-525.
** My query should be relevant to CAP users fully relying on R for multivariate
analyses, since (to my knowledge) BiodiversityR seems to be the only
package in R that does CAP as described by Anderson & Willis (2003),
i.e., estimating m through a leave-one-out procedure - unlike capscale
in Vegan.