latta: Path analysis of natural selection via survival and fecundity...

Description Usage Format Note Source References Examples

Description

Covariance matrices and syntax of the models in the paper by Latta & McCain 2009.

Usage

1
2
3
4
5
6

Format

Three covariance matrices and two character vectors containing data and model specification.

Note

The syntax in latta.greenhouse.model is that of the model in page 2463, figure 2. The vectors latta.hopland.model and latta.sierra.model represent the models in page 2465, figures 3 and 4. We get fairly similar unstandardised and standardised path coefficients, but not nearly similar maximum likelihood chi-squared values. The covariance matrices were made available by the authors in the supporting information.

Source

Article:

http://onlinelibrary.wiley.com/doi/10.1111/j.1420-9101.2009.01857.x/abstract

Supplementary information:

http://onlinelibrary.wiley.com/doi/10.1111/j.1420-9101.2009.01857.x/suppinfo

References

Latta, RG and McCain, C. 2009. Path analysis of natural selection via survival and fecundity across contrasting environments in Avena barbata. Journal of Evolutionary Biology 22: 2458-2469.

Examples

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
## Not run: 
data(latta)
cat(latta.greenhouse.model)
cat(latta.hopland.model)
cat(latta.sierra.model)

latta.greenhouse.fit <- sem(latta.greenhouse.model, sample.cov =
                            latta.greenhouse.cov, sample.nobs = 188)
latta.hopland.fit <- sem(latta.field.model, sample.cov =
                         latta.hopland.cov, sample.nobs = 188)
latta.sierra.fit <- sem(latta.field.model, sample.cov =
                        latta.sierra.cov, sample.nobs = 188)

summary(latta.greenhouse.fit, standardize = TRUE)
summary(latta.hopland.fit, standardize = TRUE)
summary(latta.sierra.fit, standardize = TRUE)

## End(Not run)


Search within the stremo package
Search all R packages, documentation and source code

Questions? Problems? Suggestions? or email at ian@mutexlabs.com.

Please suggest features or report bugs with the GitHub issue tracker.

All documentation is copyright its authors; we didn't write any of that.