nissy - Where is nissy?

	Commit message (Collapse)	Author	Age	Files	Lines
*	Removed some code preparing for moving optimal solver away from general ↵	Sebastiano Tronto	2022-09-06	1	-89/+55
\| \| \| \| \| \|	coordinate solving. Kept symcoord for coordinate solving.
*	Symcoord version of nissy. Interesting idea, but performance are	Sebastiano Tronto	2022-09-06	1	-8/+268
\| \| \| \|	actually slower. AT THIS STAGE NISSY IS NOT USABLE.
*	Removed array-size constants for certain objects (steps, commands...)	Sebastiano Tronto	2022-02-27	1	-46/+2
\|
*	Added two-phase solver	Sebastiano Tronto	2021-12-26	1	-0/+46
\|
*	some progress	Sebastiano Tronto	2021-12-17	1	-2/+1
\|
*	Faster optimal solver.	Sebastiano Tronto	2021-12-13	1	-3/+5
\| \| \| \| \| \| \| \| \| \| \|	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 :)	Sebastiano Tronto	2021-12-09	1	-1/+1
\|
*	Little performance improvement in optimal solver - more to come!	Sebastiano Tronto	2021-12-07	1	-0/+2
\|
*	Multithreading seems to be working now, it was easier than expected!	Sebastiano Tronto	2021-11-20	1	-1/+1
\|
*	Load all necessary pruning tables for a step before the actual solving process	Sebastiano Tronto	2021-11-15	1	-0/+2
\| \| \| \| \|	starts. This is in preparation for multi-threaded solving (but don't get hyped, it will take time).
*	Rewritten from scratch. Welocme nissy 2.0!	Sebastiano Tronto	2021-11-11	1	-0/+10