| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2025-08-12 | Renamed UNIX build script to build.sh, added info to README.md related to ↵ | Sebastiano Tronto | 1 | -1/+1 | |
| windows build | |||||
| 2025-08-12 | Small improvemen to python example | Sebastiano Tronto | 1 | -5/+7 | |
| 2025-08-11 | Simplified name of Python module | Sebastiano Tronto | 3 | -9/+14 | |
| 2025-08-08 | Small fixes | Sebastiano Tronto | 3 | -6/+7 | |
| 2025-08-07 | Added API function for solution variations | Sebastiano Tronto | 1 | -0/+12 | |
| 2025-07-18 | Added simpler python example | Sebastiano Tronto | 1 | -0/+10 | |
| 2025-04-17 | Small rework of optimal vs maxsols | Sebastiano Tronto | 1 | -1/+1 | |
| I wanted to make the "optimal" and "maxsolutions" options mutually exclusive, but in the end I decided there is value in keeping both (e.g. for specifying a limit to the number of solutions when asking for "all" optimal"). Now optimal cannot be negative anymore, for the same reason of maxsolutions. The interface user (shell, UI) will have to take care of handling this in a way that makes sense for the user. Usually this means setting the maximum number of solutions to UINT_MAX (or a similar very high number) when the user wants "all optimal". | |||||
| 2025-04-14 | Improved C++ API and added info to README | Sebastiano Tronto | 1 | -0/+37 | |
 |
index : nissy-core | |
| The "engine" of nissy, including the H48 optimal solver. |
| aboutsummaryrefslogtreecommitdiff |
Generated with cgit - Back to sebastiano.tronto.net