nissy/src/steps.h, branch master Where is nissy? https://git.tronto.net/nissy/atom?h=master 2023-05-01T14:33:51Z Split nissy in other repos, see README.md 2023-05-01T14:33:51Z Sebastiano Tronto sebastiano@tronto.net 2023-05-01T14:33:51Z urn:sha1:bf44088d4373a9520e860152c56a958332819c4b I made a mess, but it works. Still need to implement new optimal solver. 2023-03-05T09:13:01Z Sebastiano Tronto sebastiano@tronto.net 2023-03-05T09:13:01Z urn:sha1:87a15e960e31365698df7e06cd3e6b851e17c1a5 After that, a big redesign is due. Removed some code preparing for moving optimal solver away from general coordinate solving. 2022-09-06T21:25:31Z Sebastiano Tronto sebastiano@tronto.net 2022-09-06T21:25:31Z urn:sha1:569983380edfb3744192b5a652e2ac038840e53d Kept symcoord for coordinate solving. Symcoord version of nissy. Interesting idea, but performance are 2022-09-06T16:00:40Z Sebastiano Tronto sebastiano@tronto.net 2022-09-06T16:00:40Z urn:sha1:a125e69c8ce0a2764b1e50b2dad0a4fa9d141ef4 actually slower. AT THIS STAGE NISSY IS NOT USABLE. Removed array-size constants for certain objects (steps, commands...) 2022-02-27T15:53:22Z Sebastiano Tronto sebastiano@tronto.net 2022-02-27T15:53:22Z urn:sha1:7de88d1bcd420447023b8e74b0aa4f5e8ba1df6b Added two-phase solver 2021-12-26T18:38:28Z Sebastiano Tronto sebastiano.tronto@gmail.com 2021-12-26T18:38:28Z urn:sha1:975e3eafbae15b93a1a4f160dd781d359a6c717b some progress 2021-12-17T21:03:33Z Sebastiano Tronto sebastiano.tronto@gmail.com 2021-12-17T21:03:33Z urn:sha1:6df92db4d23dd6e2c3aba48caf1e0ea30265abb2 Faster optimal solver. 2021-12-13T19:40:18Z Sebastiano Tronto sebastiano.tronto@gmail.com 2021-12-13T19:40:18Z urn:sha1:1215648b1ba3c592bd9d97b871349673d1702e44 This is a pretty big one, but unfortunately performance only improved by about 5%. I implemented one of the main ideas of nxopt, that is switching to the inverse scramble on the fly if it gives a lower branching factor. On the one hand it makes sense that it does not have such a huge impact, since it only rarely happens that we do have a lower branching factor on inverse, but on the other hand I am quite sad that the improvement is barely noticeable :-( Maybe the problem is that I have introduced a lot of new overhead and I can improve that in the future. Or maybe I am just overlooking something stupid. Multi-threaded pruning table generation - now it's actually fast :) 2021-12-08T23:42:39Z Sebastiano Tronto sebastiano.tronto@gmail.com 2021-12-08T23:42:39Z urn:sha1:8acabe18cad69d7c7ed7a00ffef654abc3873a16 Little performance improvement in optimal solver - more to come! 2021-12-07T11:20:51Z Sebastiano Tronto sebastiano.tronto@gmail.com 2021-12-07T11:20:51Z urn:sha1:b6fd508253bce9225dd24b6538adb5093892c4f8