Skip to content

freemapper-courseplan v0.13.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 19:13
· 123 commits to main since this release

Added

  • The Lübeck example has a score course in a second project file, luebeck-score.courseplan.toml: 9 controls, 25 points, 15 minutes, from score draft, with its transcript, check output, IOF XML, CSV list and evaluation sheet in English and German. A draft at 45 minutes fails because the free codes run out (30 controls at the highest value 5, 54 at 9), not because the map is small; the README says so.
  • score suggest takes --course NAME (tool parameter course): start and finish of that score course. The editor's Suggest sends the selected course; before, it used the first start of the event, which can lie inside a building.
  • A failed draft whose control count is capped by the free codes says so (hint "raise the highest value or free codes") instead of blaming the map.
  • info names controls, points and time limit of a score course. It used to say that the length was not supported.
  • Score courses in the exports. The IOF XML now holds score courses with the value of each control in CourseControl/Score; time limit, penalty and mandatory links sit in an Extensions element, because the schema has no place for them. New export --csv FILE --course NAME writes code, value and position of the controls, and export --sheet FILE --course NAME writes an evaluation sheet with the time limit, the penalty, the rule that the faster runner wins on equal points and the rule that a runner who skips a link is disqualified (tools export_score_csv, export_score_sheet). The Purple Pen export still skips score courses and says so. The IOF XML has not been tried in OE (ADR 0070).
  • The editor draws score courses and has a Score panel: a suggestion with candidate markers and their values, "Accept" for a single candidate, a draft with a length report, "Apply" and a progress line while the program computes. Mandatory links appear as dashed lines between their controls. Candidates and drafts are not saved until you accept or apply them. A long run no longer stops the editor from noticing changes to the file (ADR 0069).
  • score suggest, score draft and score length (tools score_suggest, score_draft, score_length): ranked control sites from the map, a draft of a score course whose length meets the bands of both runner profiles, and the length analysis of an existing course. Only draft --apply writes; it creates the course or replaces the controls of a score course, and the editor can undo it. A draft that misses a band exits with 1 and names each miss and a hint. Sites stay 4 m away from forbidden routes (ADR 0068).
  • Editing score courses on the command line, over MCP and in the editor's operations: course add --kind score --time-limit N, score controls, score value, score link add|remove, score settings and score course set, with the tools add_score_course, set_score_controls, set_control_value, add_score_link, remove_score_link, set_score_settings and set_score_course_details. The code decides a control's value, so a different value is refused. Without a penalty a score course stores none and uses the default (the highest control value, at least value_max); --no-penalty goes back to it. Recoding a control gives it the value of its new code. rename, remove, classes and print scale work on score courses; legs, bends and numbers stay with individual courses (ADR 0067).
  • Score courses: the project has a [score] table with the value range, runner profiles and seed, and a score course can name mandatory links between two controls. Loading a project refuses links to unknown controls, duplicate links and branching chains (ADR 0060).
  • check now checks score courses: value in the code, codes, ring and order of the controls, length, time limit, penalty, mandatory links and mix. Team and relay courses stay skipped (ADR 0066).

Changed

  • Score fixes before the first release: a suggested control always has a route in the tours, a length report never says "inf percent", the speed table treats forest 405 as good running (1.1) and the railway helper 515.1 as no wall, and score suggest shows route choice and difficulty to two decimals and seconds to one. score settings --value-max refuses a value below that of an existing control.
  • Score fixes before the first release: a suggested control always has a route in the tours, a length report never says "inf percent", the speed table treats forest 405 as good running (1.1) and the railway helper 515.1 as no wall, and score suggest shows route choice and difficulty to two decimals and seconds to one. score settings --value-max refuses a value below that of an existing control.
  • The tool descriptions of check and export_iof_xml no longer say that score courses are not checked or written. README, manual, glossary, design and AGENTS.md describe score courses as built.
  • Internal: the map kind, the sidecar reader and the object class now come from freemapper-core v0.19.0 (freemapper-contract) instead of local copies. Names and output stay the same.

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.13.0-windows-x86_64.zip
  • macOS Apple Silicon (M1 and newer): freemapper-courseplan-v0.13.0-macos-arm64.tar.gz
  • macOS Intel: freemapper-courseplan-v0.13.0-macos-x86_64.tar.gz
  • Linux: freemapper-courseplan-v0.13.0-linux-x86_64.tar.gz (ARM: linux-arm64)

Full Changelog: v0.12.0...v0.13.0