z-logo
Premium
NEW INTERPRETATION OF THE INFLORESCENCE OF FAGUS DRAWN FROM THE DEVELOPMENTAL STUDY OF FAGUS CRENATA, WITH DESCRIPTION OF AN EXTREMELY MONSTROUS CUPULE
Author(s) -
Okamoto Motoharu
Publication year - 1989
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.1002/j.1537-2197.1989.tb11279.x
Subject(s) - inflorescence , biology , bract , botany , fagus crenata , phyllotaxis , beech , shoot , meristem
The inflorescence of Fagus is generally considered to be a determinate one, i.e., an axillary dichasium, in contrast to those of most genera in the family, which are indeterminate, dichasial, or simple catkins. To understand the relationship between the two types, ontogenetic development of the inflorescence of Fagus crenata was investigated. The early developmental stages are similar in both the male and the female inflorescences. At first, the inflorescence is oval‐shaped, then a swelling forms at the distal side of it. Subsequently, another swelling forms at the proximal side. The more or less conspicuous residual part of the primary inflorescence axis remains between the two swellings. The inflorescence becomes heart‐shaped and the first flower forms at the summit of each swelling. Subsequently, higher‐ordered flowers form dichasially in the male inflorescence, and the cupule valves differentiate in the female one. This organogenetic manner suggests that the inflorescence of Fagus is an indeterminate one, consisting of two dichasia arranged alternately on the primary axis. The scale leaves surrounding the inflorescence were also given a new interpretation. They were considered to be stipules of the bracts, because sometimes they constitute a continuous structure, together with an inconspicuous swelling between them. A proliferous‐type monstrous cupule was interpreted as supporting evidence for the hypothesis.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here