Is possible use s-metolachlor as pre-emergence herbicide in sesame crop ?
- User
Is possible use s-metolachlor as pre-emergence herbicide in sesame crop ?
Assistant
Yes, S-metolachlor can be used as a pre-emergence (PRE) herbicide in sesame crops, but its application requires careful management to avoid crop injury. Key findings from research include:
Effectiveness and Safety
- Registered use: S-metolachlor is the only herbicide registered for PRE use in the U.S. for sesame cultivation[2][3][10].
- Weed control: It provides excellent control of grassy weeds (93% efficacy) but performs poorly against broadleaf weeds[4].
- Crop tolerance:
- Low injury risk at recommended doses (e.g., 1.43 kg ai/ha) when applied 3–6 days after planting (DAP), with minimal stunting (2% at 6 weeks after treatment)[6].
- Higher injury risk at elevated doses (e.g., 2.86 kg ai/ha) or when applied immediately after planting, causing stunting (up to 46%) and yield reductions[2][6].
Critical Factors for Safe Use
- Application timing:
- Delaying application by 3–6 days post-planting improves seedling emergence (89–92% vs. 55–63% with immediate application)[6].
- Early applications (e.g., 3 days before planting) reduce yield by 22–33%[6].
- Dose adjustments:
- Lower doses (1.43 kg ai/ha) minimize injury, while higher doses (2.86 kg ai/ha) increase phytotoxicity[2][6].
- Environmental interactions:
- Injury severity varies by location and soil type (e.g., sandy soils may increase risk)[2][6].
Comparisons with Other Herbicides
- Diuron: Often used in combination with S-metolachlor, but tank mixtures can reduce sesame plant populations[4].
- Pendimethalin: Another PRE herbicide, but S-metolachlor remains the primary registered option in the U.S.[10].
Conclusion
S-metolachlor is viable for PRE weed control in sesame when applied post-planting (3–6 DAP) at recommended rates. However, improper timing or excessive doses can lead to stunting and yield loss, necessitating careful adherence to guidelines[2][3][6].
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
sonarCompare side by side →
- gpt-4o-search-preview-highCompare side by side →
- gpt-4o-search-previewCompare side by side →
sonar-proCompare side by side →
sonar-pro-highCompare side by side →
sonar-pro-highCompare side by side →
sonarCompare side by side →
sonar-pro-highCompare side by side →
- gpt-4o-search-preview-highCompare side by side →
sonarCompare side by side →
sonar-reasoningCompare side by side →