z-logo
Premium
Yield‐component Analysis of Oat Isolines that Produce Different Grain Yields 1
Author(s) -
Brinkman M. A.,
Frey K. J.
Publication year - 1977
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/cropsci1977.0011183x001700010043x
Subject(s) - panicle , tiller (botany) , avena , biology , agronomy , rust (programming language) , yield (engineering) , grain yield , cultivar , crown (dentistry) , poaceae , fructification , horticulture , materials science , metallurgy , medicine , dentistry , computer science , programming language
A series of early and midseason isolines of oats ( Avena sativa L.) contain specific crown‐rust resistance loci, which were associated with significant grain‐yield deviations when tested in rust‐free conditions. To delineate specific causes for these yield deviations, yield components were measured in the isolines and their recurrent parents in six rust‐free environments. Increased grain yields in both isolines with the crownrust resistance allele from CI 8079, an Avena sterilis L. strain from Israel, were due primarily to significantly increased tiller production. A 3.0% increase in spikelets per panicle also contributed to the increased yield of CI 9170, the early‐maturing isoline. Although each donor parent was associated with contrasting yield‐component expressions in the early and midseason backgrounds in the remaining isoline sets, causes of deviant yields were evident. An increase in panicle number contributed to grain‐yield advantages of isolines derived from CI 7171, while seed weight improvement was the most important contributor to yield improvement in the midseason isoline. The significant yield reductions of X5501 and CI 9192, the early and midseason isolines with crown‐rust resistance derived from Arena strigosa Schreb., were caused primarily by fewer spikelets per panicle.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here