nissy-core/tools/302_solve_multisol, branch intertwined-fallback-tableThe "engine" of nissy, including the H48 optimal solver.https://git.tronto.net/nissy-core/atom?h=intertwined-fallback-table2025-07-31T11:42:33ZFixed table name in tools2025-07-31T11:42:33ZSebastiano Trontosebastiano@tronto.net2025-07-31T11:41:29Zurn:sha1:474039de7af2cee7fa309e06a5c4e75b81f220adDo all loggin in main thread2025-05-23T14:54:59ZSebastiano Trontosebastiano@tronto.net2025-05-23T14:48:58Zurn:sha1:c6a77f30f64be73a5e55e06336975f2ecfbb2324
Before this committ, the solver (via the generic solution-appender
routines in src/solve/solutions.h) and the H48 data generator did some
logging in the worker threads, without using any locks. This was not nice,
but in practice it did not cause any problem, because the log messages
were rare.
However, this turned out to be a problem when building to WASM, because
web workers do not have access to the main JS memory, and therefore
they cannot call functions from the main JS. This includes not only the
callback functions for logging, but also those for polling the status
of the solver (run / pause / stop).
This commit fixes this at the cost or being somewhat inelegant: the
solutions are not logged as they are found, but only every 500ms.
Added stop / pause / resume solve to API2025-04-29T08:08:04ZSebastiano Trontosebastiano@tronto.net2025-04-29T08:08:04Zurn:sha1:8d3fc9f5f9c0593fcae9c451efe6c89c64dcbe84Removed old scripts and updated public API2025-04-22T07:00:15ZSebastiano Trontosebastiano@tronto.net2025-04-22T07:00:15Zurn:sha1:8b72e391c7185e3da0dfbf0ab60068ac37e4d5ccAlways use unsigned char * for data buffers2025-04-21T12:44:07ZSebastiano Trontosebastiano@tronto.net2025-04-21T12:33:01Zurn:sha1:510a7471348788fccba6b7c4b9f7b7cc9aee6ba9
Before this commit I was inconsistently using one of void *, char *
and uint8_t *.
Restore logging to stderr for tools2025-04-17T12:36:47ZSebastiano Trontosebastiano@tronto.net2025-04-17T12:36:47Zurn:sha1:c182f3f16e56e9533060ffa06b25391e239a28eeBetter logging function2025-04-15T13:51:40ZSebastiano Trontosebastiano@tronto.net2025-04-15T13:51:40Zurn:sha1:b25a939e2d8b045c083caf3264c4e5aac1cf88fb
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.
Some minor changes to the interface.2025-04-08T13:16:21ZSebastiano Trontosebastiano@tronto.net2025-04-08T13:16:21Zurn:sha1:e4f356b9592599ad91aac34bf2265c9bcdfbb81f
- 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 solverinfo2025-03-14T15:18:29ZSebastiano Trontosebastiano@tronto.net2025-03-14T15:18:29Zurn:sha1:1e1fd628207034b0412c50e289f146d34c5baf71Revert "Temporary fix for tools"2025-03-12T14:40:48ZSebastiano Trontosebastiano@tronto.net2025-03-12T14:40:48Zurn:sha1:45eddc73d44f59d82fcf93e2213bb972c6b7c86a
This reverts commit 4d0e55e9def2ba1eaca5b2289ca5b30e951f4d97.