z-logo
Premium
A Diallel Study of Bract Surface Area/Lint Weight per Boll Ratio in Cotton 1
Author(s) -
Bowman D. T.,
Jones J. E.
Publication year - 1984
Publication title -
crop science
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.76
H-Index - 147
eISSN - 1435-0653
pISSN - 0011-183X
DOI - 10.2135/cropsci1984.0011183x002400060031x
Subject(s) - lint , diallel cross , biology , epistasis , bract , heritability , gossypium , allele , overdominance , dominance (genetics) , zoology , field experiment , genetics , horticulture , agronomy , gene , hybrid , inflorescence
A seven parent diallel study was conducted to determine the inheritance of the ratio bract surface area per lint weight per boll in cotton ( Gossypium hirsutum L.). Experiments were performed in the field at Alexandria and Baton Rouge, LA in 1978 and 1979, and included the seven parents, their 21 F 1 's and their 21 F 2 's. Inbreeding depression and F 2 deviations were insignificant, suggesting that epistasis and dominance were not as important as additive effects. Partial failure of the assumptions of no epistasis, no multiple allelism, and independent gene distribution was observed in the three general tests. Epistasis and multiple allelism were specifically tested and found to be negligible. Genotype‐environment interaction assumptions were specifically tested, and the additive and dominance effects were found to deviate among environments. A significant year‐array interaction indicated that dominance relationships among parents were not constant between years, suggesting that one needs to test over years. Partial dominance was expressed at most loci where dominant alleles effected the bract surface area per lint weight per boll ratio, and these dominant alleles were effecting smaller ratios. Narrow‐sense heritability estimates ranged from 0.20 to 0.92 and averaged 0.47, indicating that nearly one‐half of the heritability was additive in nature.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here