z-logo
Premium
Reproductive effort and costs of reproduction do not explain female‐biased sex ratios in the moss Pseudocalliergon trifarium (Amblystegiaceae)
Author(s) -
Bisang Irene,
Ehrlén Johan,
Hedenäs Lars
Publication year - 2006
Publication title -
american journal of botany
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.218
H-Index - 151
eISSN - 1537-2197
pISSN - 0002-9122
DOI - 10.3732/ajb.93.9.1313
Subject(s) - biology , sex ratio , reproduction , sporophyte , sexual reproduction , moss , demography , zoology , ecology , botany , population , sociology
A fundamental assumption in life‐history theory is that reproduction is costly. Higher reproductive investment for fruits than for flowers may result in larger costs of reproduction in females than in males, which is often used to explain male‐skewed sex ratios in unisexual seed plants. In contrast, bryophytes have predominantly female‐biased sex ratios, suggested to be a product of a higher average cost of sexual reproduction in males. Empirical evidence to support this notion is largely lacking. We investigated sex‐specific reproductive effort and costs in the unisexual moss Pseudocalliergon trifarium that has a female‐dominated expressed sex ratio and rarely produces sporophytes. Annual vegetative segment mass did not differ among male, female, and non‐expressing individuals, indicating that there was no threshold‐size for sex expression. Mean and annual mass of sexual branches were higher in females than in males, but branch number per segment did not differ between sexes. Prefertilization reproductive effort for females was significantly greater (11.2%) than for males (8.6%). No cost for sexual branch production in terms of reduced relative vegetative growth or decreased investment in reproductive structures in consecutive years was detected. A higher realized reproductive cost in males cannot explain the unbalanced sex ratio in the study species.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here