Response of four market classes of dry bean to acifluorfen, bentazon, and bentazon/acifluorfen applied postemergence
Bibliographic record
Abstract
Abstract Three distinct studies consisting of a total of 11 field trials were carried out from 2016 to 2019 in Ontario to assess the tolerance of four market classes of dry bean to acifluorfen, bentazon, and bentazon/acifluorfen applied postemergence (POST) at various rates. In Study 1, acifluorfen (265 and 530 g ai ha −1 ) and bentazon (577 and 1144 g ai ha −1 ) caused up to 13% and 8% visible injury, respectively, but did not affect the relative stand, height, seed moisture, or yield of dry bean. Bentazon/acifluorfen (842 and 1684 g ai ha −1 ) caused up to 32% visible injury in dry bean but did not affect the relative stand, height, moisture, or seed yield except at the 2× rate which reduced dry bean biomass, height, and yield 43%, 11%, and 11%, respectively. The preformulated mixture of bentazon/acifluorfen caused a synergistic increase in dry bean injury. In Study 2, acifluorfen (600 and 1200 g ai ha −1 ) and bentazon (1080 and 2160 g ai ha −1 ) injured dry bean up to 12% and to 9%, respectively, but did not affect the relative stand, height, moisture, or yield. Bentazon/acifluorfen (840 and 1680 g ai ha −1 ) injured dry bean up to 16% but did not affect the relative stand, height, moisture, or yield of dry bean except at the high rate which reduced biomass, height, and yield 17%, 9%, and 5%, respectively. In Study 3, acifluorfen (420 and 480 g ai ha −1 ) and bentazon (1080 and 2160 g ai ha −1 ) injured dry bean up to 24 and 16%, respectively, but did not affect the relative stand, height, seed moisture content, or yield except for the relative biomass which was reduced up to 17%. Bentazon/acifluorfen (840 and 1680 g ai ha −1 ) injured dry bean up to 45% but did not affect the relative stand, height, seed moisture, or yield except for biomass, height, and seed yield which were decreased 44%, 11%, and 12% at the high rate. This study concludes that acifluorfen alone or preformulated with bentazon applied POST at rates assessed cannot be safely used dry bean.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".