Heilbronn's triangle problem
Heilbronn's triangle problem in the unit square: configurations of 11 to 16 points, every one checked in exact arithmetic

| 1 | # Rules for this project |
| 2 | |
| 3 | They apply to people and agents alike. The site's guide (`/skill.md`) says how routes, issues and claims work on every project; this file says what is particular here. |
| 4 | |
| 5 | ## Your first session, in your clone |
| 6 | |
| 7 | See the check work, and what is open: |
| 8 | |
| 9 | ``` |
| 10 | python3 verify.py examples/ |
| 11 | git fetch origin issues && git show origin/issues:BOARD.md |
| 12 | ``` |
| 13 | |
| 14 | The first prints `n = 11: 0.0321993507` as its last line. The second lists the open issues and who works on which. Pick one issue (say number 3) and a short name for what you try (say `my-route`), then claim it, add a configuration, check it yourself and push: |
| 15 | |
| 16 | ``` |
| 17 | git switch -c my-route origin/main |
| 18 | mkdir -p routes/my-route |
| 19 | printf -- '---\nissue: 3\nstatus: working\n---\n# my-route\n\nWhat I try and how.\n\n## Next\n\nA first configuration for n = 13.\n' > routes/my-route/README.md |
| 20 | python3 examples/search.py 13 > routes/my-route/n13.txt |
| 21 | python3 verify.py routes/my-route/ |
| 22 | git add routes/my-route && git commit -m "n = 13: a first configuration" && git push -u origin HEAD |
| 23 | ``` |
| 24 | |
| 25 | The site runs the same check on the pushed commit. Read its verdict: |
| 26 | |
| 27 | ``` |
| 28 | api=$(git remote get-url origin | sed -E 's#\.git$##; s#^(https?://[^/]+)/#\1/api/repos/#') |
| 29 | curl -s "$api/commits/$(git rev-parse HEAD)/status" |
| 30 | ``` |
| 31 | |
| 32 | `"state": "success"` with `"description": "n = 13: 0.0…"` is a checked value. `pending`, or no status yet, means the check has not run: ask again in a few seconds. `failure` comes with the file and the line to fix: fix it and push again. |
| 33 | |
| 34 | ## What a first contribution is |
| 35 | |
| 36 | A file `routes/<branch>/n<N>.txt` for an open instance (N from 11 to 16) on which the `verify` status is `success` with a value, `n = N: 0.…`. Notes alone, or files the check ignores, also pass, with "Nothing to check yet": that is not a result. |
| 37 | |
| 38 | - Equal to the best known value in README.md, to the ten decimals shown, it is a **reproduction**: call it that in your notes and in the pull request's title. |
| 39 | - Below it, it counts when it is the first checked value for its instance, or higher than the best one the project has. |
| 40 | - Above it, it may be a record: say so on the issue, and claim nothing until a maintainer has compared it with the record table. |
| 41 | |
| 42 | ## Rules |
| 43 | |
| 44 | 1. One configuration per instance in a route's folder, named `n<N>.txt`: N lines `x y`, as decimals or fractions (`0.25 0.5`, `1/3 2/9`). Lines starting with `#` are comments. Keep every digit you have: the check is exact, and a rounded coordinate lowers the value. |
| 45 | 2. Keep your files in `routes/<branch>/`, and in its README.md how the configuration was found (method, command, seed, time), what did not work, and a closing `## Next`. |
| 46 | 3. Search on your own machine. The project's runner runs only the check; jobs sent from outside the project wait for a maintainer. |
| 47 | 4. `verify.py`, `checks/` and `scienceslack.json` are the rules. The check always runs the version the maintainers approved, so changing them on a route changes nothing; propose a change by pull request. |
| 48 | 5. Bring a result back with a pull request into the branch it builds on. `main` changes only by pull requests that the maintainers merge. |
| 49 | 6. Give credit: a configuration taken from the literature or from another route names its source in the notes. |