nissy - Where is nissy?

	Commit message (Collapse)	Author	Age	Files	Lines
*	Split nissy in other repos, see README.md	Sebastiano Tronto	2023-05-01	1	-122/+0
\|
*	Some fixes	Sebastiano Tronto	2023-03-05	1	-0/+3
\|
*	I made a mess, but it works. Still need to implement new optimal solver.	Sebastiano Tronto	2023-03-05	1	-440/+73
\| \| \| \|	After that, a big redesign is due.
*	Added (just a few) tests for alg and added fields to alg struct	Sebastiano Tronto	2023-02-10	1	-19/+5
\|
*	Removed some code preparing for moving optimal solver away from general ↵	Sebastiano Tronto	2022-09-06	1	-57/+76
\| \| \| \| \| \|	coordinate solving. Kept symcoord for coordinate solving.
*	Symcoord version of nissy. Interesting idea, but performance are	Sebastiano Tronto	2022-09-06	1	-244/+225
\| \| \| \|	actually slower. AT THIS STAGE NISSY IS NOT USABLE.
*	Added dr and htr scrambles	Sebastiano Tronto	2022-03-02	1	-1/+7
\|
*	Changed unniss() to return an Alg*. Addedd inplace() to run a function on an ↵	Sebastiano Tronto	2022-02-27	1	-1/+1
\| \| \| \|	alg in place.
*	Removed possible cancellable moves from 2phase solver	Sebastiano Tronto	2022-02-25	1	-2/+5
\|
*	Fixed bug in using niss	Sebastiano Tronto	2022-02-21	1	-1/+1
\|
*	Added scramble command	Sebastiano Tronto	2021-12-26	1	-1/+1
\|
*	Added two-phase solver	Sebastiano Tronto	2021-12-26	1	-0/+51
\|
*	Better trans-detection system (for e.g. drfin for HTR scramble)	Sebastiano Tronto	2021-12-26	1	-24/+49
\|
*	Added -O option for solve (specify number of moves within optimal)	Sebastiano Tronto	2021-12-25	1	-3/+6
\|
*	Transform solutions early so that -v gives meaningful info	Sebastiano Tronto	2021-12-25	1	-11/+15
\|
*	Fixed bug that prevented switching depending on branch factor (leftover from ↵	Sebastiano Tronto	2021-12-24	1	-3/+0
\| \| \| \|	previous debugging)
*	some progress	Sebastiano Tronto	2021-12-17	1	-2/+3
\|
*	Added a new pruning table (equivalent to nxopt31). I have not tested it yet, ↵	Sebastiano Tronto	2021-12-16	1	-37/+43
\| \| \| \| \| \| \|	it takes a while to generate. Plus I have done a whole lot of refactoring in random places because I cannot focus on one thing at the time.
*	Faster optimal solver.	Sebastiano Tronto	2021-12-13	1	-120/+194
\| \| \| \| \| \| \| \| \| \| \|	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
\|
*	Just refortmatting and added one type	Sebastiano Tronto	2021-12-08	1	-3/+3
\|
*	Little performance improvement in optimal solver - more to come!	Sebastiano Tronto	2021-12-07	1	-52/+73
\|
*	Multithreading seems to be working now, it was easier than expected!	Sebastiano Tronto	2021-11-20	1	-23/+170
\|
*	Load all necessary pruning tables for a step before the actual solving process	Sebastiano Tronto	2021-11-15	1	-20/+9
\| \| \| \| \|	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/+173