nissy - Where is nissy?

	Commit message (Collapse)	Author	Files	Lines
2022-03-15	Prepare for big changes in coordinates	Sebastiano Tronto	1	-16/+16

2022-03-12	Added freemem command	Sebastiano Tronto	1	-1/+13

2022-03-03	Added messages about generating pruning tables	Sebastiano Tronto	1	-2/+2

2022-02-27	Removed some unused code (khuge). Improved optimal solver performance by ↵	Sebastiano Tronto	1	-75/+7
	about 10% using raw transition tables (same for dr step).
2021-12-24	use nxopt31 (compressed) by default for optimal solving	Sebastiano Tronto	1	-3/+11

2021-12-23	Added the possibility to compress tables to 2 bits per entry.	Sebastiano Tronto	1	-4/+4
	This is done similarly to nxopt: one base value is selected and entries are memorized based on that base value. Values higher than base+3 are returned as base+3 (still a valid estimate) and values lower or equal to base require a lookup on a "fallback" table, which must give a valid estimate for the larger one (e.g. nxopt31 or khuge can fallback to drud_sym16). I have also added some info to the pruning table files: base value and distribution. Unfortunately this means that everyone who has used nissy 2.0beta has to re-generate the tables.
2021-12-17	some progress	Sebastiano Tronto	1	-9/+0

2021-12-16	Added a new pruning table (equivalent to nxopt31). I have not tested it yet, ↵	Sebastiano Tronto	1	-28/+57
	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.
2021-12-08	Faster and nice pruning table generation. Can still be improved with ↵	Sebastiano Tronto	1	-15/+100
	multithreading.
2021-11-17	Use inttypes.h macros to print uint64_t variables (this requires -std=c99). ↵	Sebastiano Tronto	1	-1/+1
	Added a couple of TODOs
2021-11-12	I tried to remove the dependence on antindex in order to get rid of them	Sebastiano Tronto	1	-0/+9
	once and for all. I successfully removed from the pruning table generation part by using an alternative (slower) method, but then I realized that I also use antindexes when generating symmetry data. So I reverted to the original pruning table computation method, but I left the alternative way there, commented.
2021-11-11	Rewritten from scratch. Welocme nissy 2.0!	Sebastiano Tronto	1	-0/+355