z-logo
Premium
Susceptibility of intercrops to infection with Rhizoctonia solani AG 2‐2 IIIB and influence on subsequently cultivated sugar beet
Author(s) -
Kluth C.,
Buhre C.,
Varrelmann M.
Publication year - 2010
Publication title -
plant pathology
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.928
H-Index - 85
eISSN - 1365-3059
pISSN - 0032-0862
DOI - 10.1111/j.1365-3059.2010.02274.x
Subject(s) - sugar beet , rhizoctonia solani , biology , brassica rapa , raphanus , rhizoctonia , agronomy , intercropping , horticulture , sclerotinia sclerotiorum , sugar , brassica , biochemistry
The susceptibility of intercrop species ( Raphanus sativus , Brassica juncea , B. rapa , Sinapis alba and Phacelia tanacetifolia ) to the sugar beet pathogen Rhizoctonia solani was investigated in vitro , in the greenhouse and in the field with artificial inoculation. Disease severity in subsequently cultivated sugar beet was monitored in the field. Differences in susceptibility between species were found to be consistent in all experimental systems. All intercrop species were susceptible to R. solani. Brassica rapa and R. sativus were less susceptible than P. tanacetifolia . Compared to fallow, the cultivation of B. rapa and R. sativus reduced disease severity in subsequently grown sugar beet (median ratings of up to 3·0 and 3·5, respectively, depending on environmental conditions). This resulted in higher white sugar yield compared to fallow (up to 210% and 157% for B. rapa and R. sativus , respectively). This study demonstrates that in vitro and greenhouse resistance tests are suitable systems to predict the effects of intercrop species susceptibility in the field on disease severity and white sugar yield in subsequently grown sugar beet. Intercrop breeding programmes might profit from fast and efficient screening tests to provide Rhizoctonia ‐resistant intercrops as an additional control measure against R. solani in sugar beet.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here