From d13ee2865332b2bc5c2fd45a7c4973cb29b3887d Mon Sep 17 00:00:00 2001 From: AJ Isaacs Date: Tue, 29 Sep 2026 20:49:16 -0400 Subject: [PATCH] docs(template): retire the model competition and open engines to each other Engines now target job lanes; a change lands when it beats the lane's current best on the benchmark. Reading and borrowing from other engines is allowed with credit, replacing the isolation/disqualification rule. --- _Template/BENCH-RULES.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/_Template/BENCH-RULES.md b/_Template/BENCH-RULES.md index ec61407..22c185d 100644 --- a/_Template/BENCH-RULES.md +++ b/_Template/BENCH-RULES.md @@ -1,15 +1,15 @@ # Bench rules -These rules apply to every model building or optimizing an OpenNest engine, so results can be -compared fairly. `README.md` in this folder covers what counts as an independent engine; this -file covers how the run itself works. +These rules apply to every model building or optimizing an OpenNest engine. Engines are no longer +a competition between models: each engine targets a job lane (rectangles, circles, rings, +irregular), and a change lands only when it beats that lane's current best on the benchmark. +`README.md` in this folder covers what counts as an engine; this file covers how the run works. ## Your workspace - You are working in a copy of OpenNest. Your engine is `Engines/OpenNest.Engine.__NAME__/`. -- Work only inside this copy. Do not search the rest of the filesystem, other checkouts of - OpenNest, the network, or any git remote for other nesting engines or earlier versions of - this project. Using another engine's code or results in any form is disqualifying. +- Other engines in OpenNest-Engines are open to read, compare against and borrow from. Credit + borrowed ideas in your report. Do not edit another engine's folder in the same change. - Do not edit `OpenNest.Core`, `OpenNest.Engine`, `OpenNest.Benchmark` or anything else outside your engine folder, except for throwaway tools under `tools/` and scratch work under `bench-local/` (see below). If shared code has a bug that blocks you, work around it in your @@ -36,7 +36,7 @@ file covers how the run itself works. part numbers inside your engine folder. The engine folder may be published; these drawings are customer property. Keep manifests, results and notes that reference the archive under `bench-local/` in the copy's root instead. -- Final scoring also uses jobs you will not see. Tune for real parts in general, not for the +- Acceptance also uses jobs you did not tune on. Tune for real parts in general, not for the specific drawings you tested with. ## Tests and scoring