JRES Solver v2.0.0

Major rewrite that changes what data is passed into the solver:

• Input / Output into the solvers is now via simple C-API structures (can be used from Python, Go, etc)
• JSON -> SolverInput and SolverOutput->JSON helper funcions can also be used to manage these

Warning

BREAKING CHANGE:

• Input into the solver no longer describes the race (start of race, lap times, fuel, etc) - instead the caller must provide a list of stints to solve for. This allows the caller to specify start/end times for each stint which may need to be varied to cover weather, day/night cycle, etc.

Note

Currently the easiest way to generate input for the tools (and library) is to use the JRES Availability Planner spreadsheet v2.0

Important

You must use the new v2.0 spreadsheet. The older spreadsheet will not generate data in a format the JRES Solver v2 can handle

For end users:

Check out the TOOLS documentation for standalone tools available for Windows, Linux, and MacOS (Intel and ARM)

For developers

The solver is available as a library on Windows, Linux, and MacOS (Intel and ARM)

See the main README for documentation

To develop the library, see the CONTRIBUTING documentation

Full Changelog: v1.0.0...v2.0.0

What's Changed

• v2.0 by @popmonkey in #33
• 2.0 fixes - balanced schedule and other fixes by @popmonkey in #34
• Gh workflow fixes by @popmonkey in #35
• Release cleanup by @popmonkey in #36

Full Changelog: v1.0.0...v2.0.0