Do several fast laser-weeding passes still beat one slow pass when the detector's hit rate comes from published field trials?
research/osrobot-weedsrc
With a detector fitted to two published field detection rates (88.9% at 0.2 m/s, 86.2% at 0.425 m/s), two laser-weeding passes at 4 km/h kill 0.952 in 40 min against 0.875 in 68 min for one pass at 1 km/h; the ranking holds, and the share of weeds the detector never sees (3 passes cap at 0.897 with 10% hidden) now sets the ceiling
What it found
osrobot-weedpass assumed a detector hit rate of 0.7 falling as exp(−v/2 m/s). This project fits pmax·exp(−v/vblur) through two published detection rates (88.94% at 0.2 m/s, Frontiers in Plant Science 2022; 86.2% at 0.425 m/s, arXiv 2512.10319), giving 0.914 and 7.19 m/s, and re-runs the multi-pass sweeps (60×30 m field, 20 seeds per row, treating on the move). The detector is far better than assumed (0.846 against 0.530 at 2 km/h), so one pass at 2 km/h kills 0.842, and two passes at 4 km/h kill 0.952 in 39.8 min against 0.875 in 68.4 min for one pass at 1 km/h: fast multi-pass still wins, and a third pass adds only 0.020. With a share of weeds never seen, three passes cap at 0.996, 0.946, 0.897, 0.799 and 0.700 for 0, 5, 10, 20 and 30% hidden. Limits: two points from two different robots read from search snippets (the papers were not opened), a flat two-point fit extrapolated to 4 km/h, independent detections apart from the swept hidden share, and assumed mud, energy and false-positive figures.
A figure from its own output
Paper, code and results
More in Open-source purpose-built robots
- When does a purpose-built gantry beat a general two-link arm at tray pick-and-place?When does a purpose-built gantry beat a general two-link arm at tray pick-and-place? At 2 mm tolerance the arm wins only between 0.36 and 0.99 m of work area, and the band depends on assumed costs (stylised).
- Does co-designing an arm's link lengths and controller beat tuning the controller on a fixed body?Does co-designing an arm's link split and controller beat tuning the controller on a fixed body? Co-design gained 1.9% in held-out move time (0.283 against 0.289 s), within three-seed noise; tuning the controller mattered about 37%. Stylised, preliminary, mostly negative.
- Can a small twin of a liquid-handling bench catch protocol errors before they run, and how much pipetting error does a serial dilution tolerate?Can a small twin of a liquid-handling bench catch protocol errors before they run, and how much pipetting error does a serial dilution tolerate? It flags 366 of 522 injected faults against 100 for a syntax-only baseline, and an assumed error curve gives a final-well CV of 0.187 at 10 µL and 0.035 at 100 µL transfers (stylised, circular fault set).
- Does the real Opentrons simulator catch the protocol faults a small stdlib liquid-handling twin catches?Does the real Opentrons simulator catch the faults the stdlib liquid-handling twin catches? On the same 522 seeded faults it raises on 270 and the twin flags 366; everything the simulator catches the twin catches too, while tip reuse, a 5 µL dispense and a half-empty source pass the simulator. Mostly policy differences; the fault set was written for the twin (stylised).
- Does searching an arm’s joint count, link lengths and mount, with its controller tuned in the loop, beat a fixed three-link body at the same cost?Does searching a planar arm's joint count, links and mount, with its controller tuned, beat a fixed three-link body at equal cost? On a shelf task with a tool-down constraint, 0.95 held-out success against 0.26; on a long position-only reach, no gain (stylised, kinematic).
- How heavy must a purpose-built UAV for targeted observation be, and when does a hover-capable airframe stop being worth its weight?How heavy must a purpose-built UAV for targeted observation be, and when is a hover-capable airframe worth its weight? At 3 km out and 20 min on station a fixed wing closes at 1.27 kg against 2.14 kg for a quadrotor and 2.08 kg for a VTOL wing, and the quadrotor stops closing at 45 min (stylised, assumed constants, no flight stack run).
All 44 Open-source purpose-built robots projects →
Other research topics
Proper scoring & elicitation28Effort & peer prediction9Verification games & slashing19Detection & tolerances14Markets as routers13Prediction-market design9Paying contributors8Decentralised training systems23Digital twins & sim-to-real164LLM chip design loops40Robot manufacturing loops53Ambient AI assistant46Self-replicating manufacturing34Simulation-first design64Engineered clothing45Task-specific AI accelerators40Algorithmic chip-design loops42Open-source purpose-built robots44The software-engineering loop43Adversarial human imitation41Open-source residential construction41Autonomous multi-angle capture34Sensing, imaging and 3D31Energy supply and dense energy storage39Robot societies among people31Agentic co-design of low-cost robots27Laundry-hanging robots25Machine learning on qualitative data23Robots on the building site27Civilizations & group psychology1History & human sciences1
Produced with AI assistance (Claude). Results are from the code in this repository and are simulated or stylised unless the abstract says otherwise; nothing here implies affiliation with or endorsement by any lab, researcher or company cited. MIT licensed.