aboutsummaryrefslogtreecommitdiff
path: root/python (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Small fixesSebastiano Tronto2025-08-083-6/+7
|
* Added API function for solution variationsSebastiano Tronto2025-08-072-19/+67
|
* Added move sequence comparison functionSebastiano Tronto2025-07-311-0/+37
|
* Added simpler python exampleSebastiano Tronto2025-07-181-0/+10
|
* Refactored checkdataSebastiano Tronto2025-05-191-3/+5
| | | | | | | | Relevant changes include: - Changed the signature of nissy_checkdata(). - Removed expected_distribution.h from tools; this data is now included in each solver's src/ code. - Removed distribution check for cocsep; may add back later.
* Remove configure + make build system.Sebastiano Tronto2025-05-161-2/+2
| | | | | This commit also updates the README, cleans up some stuff and fixes some oopsies.
* Added stop / pause / resume solve to APISebastiano Tronto2025-04-291-3/+3
|
* Added orientation to getcubeSebastiano Tronto2025-04-231-4/+6
|
* Remove compose from the public APISebastiano Tronto2025-04-221-27/+0
|
* Removed old scripts and updated public APISebastiano Tronto2025-04-221-44/+15
|
* Always use unsigned char * for data buffersSebastiano Tronto2025-04-211-5/+8
| | | | | Before this commit I was inconsistently using one of void *, char * and uint8_t *.
* Small rework of optimal vs maxsolsSebastiano Tronto2025-04-172-4/+3
| | | | | | | | | | | | | | 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".
* Better logging functionSebastiano Tronto2025-04-151-2/+2
| | | | | | | Now it is possible to provide some data together with the logging function. This is useful for example in C++, where I can now provide an arbitrary callable object as data, and a simple wrapper function that call the callable object as logging function.
* Improved C++ API and added info to READMESebastiano Tronto2025-04-141-0/+0
|
* Some minor changes to the interface.Sebastiano Tronto2025-04-081-8/+4
| | | | | | | | | - Simplified logger to accept only a string, not a variadic list of args like printf(). This can still use some improvement, but now it is easier to use from other languages. - Fixed some misuses of the logger (wrong types etc) - Renamed some constants - Fixed some typos in comments.
* Replaced datasize with solverinfoSebastiano Tronto2025-03-141-10/+16
|
* Revert API changeSebastiano Tronto2025-03-121-8/+6
|
* Fixed python moduleSebastiano Tronto2025-03-091-6/+8
|
* Allow choosing number of threads when calling solve()Sebastiano Tronto2024-12-142-6/+8
|
* Finished Python moduleSebastiano Tronto2024-10-192-10/+285
|
* Add node and fallback benchmarkingSebastiano Tronto2024-10-181-1/+1
|
* Interface changes, progress with pythonSebastiano Tronto2024-10-141-12/+179
|
* Initial support for PythonSebastiano Tronto2024-10-121-0/+34

Generated with cgit - Back to sebastiano.tronto.net