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	-64/+14
\| \| \| \| \| \|	coordinate solving. Kept symcoord for coordinate solving.
*	Symcoord version of nissy. Interesting idea, but performance are	Sebastiano Tronto	2022-09-06	1	-1387/+127
\| \| \| \|	actually slower. AT THIS STAGE NISSY IS NOT USABLE.
*	Removed some unused code (khuge). Improved optimal solver performance by ↵	Sebastiano Tronto	2022-02-27	1	-31/+0
\| \| \| \|	about 10% using raw transition tables (same for dr step).
*	Removed array-size constants for certain objects (steps, commands...)	Sebastiano Tronto	2022-02-27	1	-1/+3
\|
*	Added two-phase solver	Sebastiano Tronto	2021-12-26	1	-1/+1
\|
*	Better trans-detection system (for e.g. drfin for HTR scramble)	Sebastiano Tronto	2021-12-26	1	-124/+41
\|
*	added some optimal-after-EO steps	Sebastiano Tronto	2021-12-24	1	-0/+63
\|
*	Added -c option for solve	Sebastiano Tronto	2021-12-24	1	-0/+20
\|
*	use nxopt31 (compressed) by default for optimal solving	Sebastiano Tronto	2021-12-24	1	-10/+15
\|
*	Fixes for yesterday's commit	Sebastiano Tronto	2021-12-23	1	-1/+4
\|
*	fixed typo	Sebastiano Tronto	2021-12-22	1	-2/+1
\|
*	some progress	Sebastiano Tronto	2021-12-17	1	-20/+10
\|
*	Added a new pruning table (equivalent to nxopt31). I have not tested it yet, ↵	Sebastiano Tronto	2021-12-16	1	-105/+141
\| \| \| \| \| \| \|	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.
*	fixed a bug	Sebastiano Tronto	2021-12-14	1	-0/+4
\|
*	Added light optimal solver - about 5 times slower but takes only 500Mb of RAM	Sebastiano Tronto	2021-12-14	1	-7/+119
\|
*	minor restyling	Sebastiano Tronto	2021-12-14	1	-2/+3
\|
*	little restyling	Sebastiano Tronto	2021-12-14	1	-24/+19
\|
*	random attempts	Sebastiano Tronto	2021-12-14	1	-27/+29
\|
*	Faster optimal solver.	Sebastiano Tronto	2021-12-13	1	-144/+355
\| \| \| \| \| \| \| \| \| \| \|	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	-2/+2
\|
*	Little performance improvement in optimal solver - more to come!	Sebastiano Tronto	2021-12-07	1	-105/+172
\|
*	Some attempts at using the inverse scramble to get more info for pruning ↵	Sebastiano Tronto	2021-12-03	1	-10/+23
\| \| \| \|	(optimal solving)
*	Multithreading seems to be working now, it was easier than expected!	Sebastiano Tronto	2021-11-20	1	-12/+1
\|
*	Load all necessary pruning tables for a step before the actual solving process	Sebastiano Tronto	2021-11-15	1	-0/+142
\| \| \| \| \|	starts. This is in preparation for multi-threaded solving (but don't get hyped, it will take time).
*	Unimportant fixed	Sebastiano Tronto	2021-11-12	1	-1/+1
\|
*	Rewritten from scratch. Welocme nissy 2.0!	Sebastiano Tronto	2021-11-11	1	-0/+941