MétaCan
Menu
Back to cohort
Record W3146894849 · doi:10.1139/cjps2012-167

Response of chickpea cultivars to pre- and post-emergence herbicide applications

2013· article· en· W3146894849 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueBioOne Complete (BioOne) · 2013
Typearticle
Languageen
FieldAgricultural and Biological Sciences
TopicAgronomic Practices and Intercropping Systems
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsBlightCultivarAscochytaAgronomyWeed controlBiologyWeedCrop

Abstract

fetched live from OpenAlex

Taran, B., Holm, F. and Banniza, S. 2013. Response of chickpea cultivars to pre- and post-emergence herbicide applications. Can. J. Plant Sci. 93: 279-286. Weed control is one of the major constraints of chickpea (Cicer arietinum L.) production in western Canada. There are no highly selective herbicides registered for broadleaf weed control in this crop in western Canada, consequently herbicide injury to the crop is an issue in many situations. Experiments were conducted at Saskatoon and Elrose, SK, to examine the effects of herbicide treatments on ascochyta blight severity, days to flowering, days to maturity, plant height and yield of several chickpea cultivars. Results in 2008 and 2009 showed that sulfentrazone was the safest option evaluated for broadleaf weed control in chickpea. The results also showed that although a pre-emergence application of low-rate imazethapyr caused minor levels of injury to the plants and slightly increased ascochyta blight severity, it had only minor effects on plant development and yield compared with sulfentrazone. In contrast, post-emergence applications of imazethapyr, imazamox and metribuzin increased ascochyta blight severity significantly, delayed flowering and maturity and reduced yield. The extent of the effects of pre- and post-emergence herbicide applications varied with cultivars.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.978
Threshold uncertainty score0.892

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.

Opus teacher head0.188
GPT teacher head0.255
Teacher spread0.066 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it