Skip to content

freemapper-courseplan v0.14.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 15:02
· 80 commits to main since this release

Added

  • Self-update (ADR 0076). freemapper-courseplan update replaces the program in place with the newest signed release, after asking (--check exits with 10 when a newer version exists, --yes, --version X.Y.Z, --rollback, --mode notify|install|off). The release is checked with minisign against a key built into the program, then by SHA-256 of the download and of the unpacked file, and the new file must answer --version before anything is swapped. The old file stays as freemapper-courseplan.previous. A release build looks for a newer version at most once a day, after info and when the editor starts, and prints one line on stderr; the editor shows it in its status bar. The MCP tools check_update and install_update (only with confirm: true) tell the assistant, which asks you first; the first tool result carries a note once. Builds from source never update themselves. The program sends only a fixed User-Agent to the GitHub release servers. The release workflow now signs a manifest with the secrets MINISIGN_SECRET_KEY and MINISIGN_PASSWORD of the environment release; the environment has a required reviewer, so a release asks for approval once, before it is signed and published. Unpacking by hand stays the way to reach the first release with the updater. User manual, chapter 2.
  • Examples on two maps by Remo Madella (MOO Challenge Berlin 2025), who released them on 2026-11-12 for use within the freemapper suite; this is not an open licence (ADR 0077). examples/gleisdreieck holds a 33-minute score course (27 controls, 83 points; the good runner scores 92.8 percent, the very good runner finishes after 96.1 percent of the limit), and examples/rummelsburger-bucht a sprint course with four controls, bends, a marked leg, a first aid post and three accepted hints, with its IOF XML and Purple Pen export. Both come with transcripts and check output in English and German; each folder has an ATTRIBUTION.txt. 45 minutes does not work on either map: the READMEs give the tries and the real limits. The Purple Pen file of the new example has not been opened in Purple Pen.
  • Wider pool of control sites for score courses (ADR 0073). score suggest now also uses the free ends of walls, fences, hedges, step lines, stairways and bridges, path ends and path junctions, bends and edges of paved ground, small buildings, canopies, water banks and more point symbols, each with a clarity that lowers the difficulty and never removes a site. A closed line gives all its corners. A site that cannot be routed no longer removes every site within 100 m, only those within 30 m. On the Lübeck map suggest finds 31 sites instead of 19; on a 1.8 x 2.0 km map of Berlin-Kreuzberg 183 instead of 137. Both maps hold mostly buildings, so the gain is modest; on the Kreuzberg map the draft ends at 13 controls for 30 minutes and 26 to 28 for 45, no longer bound by the pool but by the time of the very good runner.
  • Four distance settings for score courses, in metres on the ground: value1_min_m (150) keeps every control away from start and finish, so value 1 starts there; min_gap_m (100, not lower) is the least distance between two controls and replaces the scale-derived default of score suggest; max_reach_m limits the distance from the start (automatic: a quarter of the ground the good runner covers in the time limit); high_value_gap_m (200) is the least distance between two high-valued controls, the values above 0.6 of the highest. score settings (--value1-min, --min-gap, --max-reach, --auto-reach, --high-value-gap), the tool set_score_settings and the editor's Score panel set them; older project files load with the defaults. The draft keeps the high-value gap, and check warns when a score course falls below either gap (score_min_gap, score_high_gap; ADR 0072).

Fixed

  • score suggest and score draft no longer take the corners of a map frame as sites (ADR 0078). The Gleisdreieck map has a closed rectangle of symbol 501.1 around its content, and a draft used its four corners as controls.
  • score draft and score length (and check) now agree on a set. The same leg time came out a few digits apart depending on the search that made it, and the tour heuristic turned that into another tour: at the start 40,-40 of the Berlin example the draft promised 97 points and 99.8 percent, the applied course gave 96 points and 100.7 percent of the limit. Leg times are now rounded to a millisecond where they are made (ADR 0075).
  • score draft finds a set that meets both bands where one exists, and runs faster (ADR 0074). After the prefix search it now searches locally: it swaps, adds or drops a control, or moves a value up to two steps off its quantile, for at most 150 tour evaluations with the seed of the settings. On a 1.8 x 2.0 km map of Berlin-Kreuzberg every start and limit we tried (30 and 45 minutes, three starts) now meets both bands; before, the good runner landed 0.3 to 3 points above his band every time. The values of a draft are therefore not always exact quantiles. A pool that is too small still fails: on the Lübeck map 30 and 45 minutes give the good runner every point.
  • Faster route searches. The shortest-path search uses A*, one search per control reads its legs to all others, the route-choice searches of score suggest and score draft run on several threads, and the or-opt step of the tour heuristic no longer copies the tour. On the Kreuzberg map the CPU time of score draft fell from 44 to 63 s to 24 to 35 s; most of what is left is the route search of score suggest (ADR 0074).
  • Score suggestions sit less at the rim of the map and closer to the start: the pick spaces sites more densely near the start and weighs down sites at the rim. On the Lübeck example the candidates within 48 m of the rim fell from 21 of 60 to 3, and the value-1 controls moved from 360 m to 230 m from the start (ADR 0071).

Changed

  • The documentation examples examples/luebeck-sprint and examples/berlin-kreuzberg are gone, replaced by the two examples above. The Lübeck project, its Purple Pen and IOF XML exports and its score project stay as test fixtures in tests/fixtures/luebeck-sprint/. The test berlin_score_example_meets_its_bands_and_check_is_quiet became gleisdreieck_score_example_meets_its_bands_and_check_is_quiet.

Download the archive for your system, unpack it and start freemapper-courseplan
(Windows: freemapper-courseplan.exe) from a terminal or register it with your AI assistant.
Installation and first steps: see README.md (Deutsch) / README.en.md (English) in the
archive or https://github.com/HenryJobst/freemapper-courseplan#readme

  • Windows: freemapper-courseplan-v0.14.0-windows-x86_64.zip
  • macOS Apple Silicon (M1 and newer): freemapper-courseplan-v0.14.0-macos-arm64.tar.gz
  • macOS Intel: freemapper-courseplan-v0.14.0-macos-x86_64.tar.gz
  • Linux: freemapper-courseplan-v0.14.0-linux-x86_64.tar.gz (ARM: linux-arm64)

The .gz files and freemapper-courseplan-update.json with its signature are for freemapper update.

Full Changelog: v0.13.0...v0.14.0