3 ms·
I'll have to give this a go. I'll probably fail miserably but it sounds like fun. Related: [1] Here is my (sophomoric) attempt at a compression algorithm, and [
by zelon88 7y ago
I'll have to give this a go. I'll probably fail miserably but it sounds like fun. Related: [1] Here is my (sophomoric) attempt at a compression algorithm, and [2] here is the blog post I wrote about it.
[1] https://github.com/zelon88/xPress https://github.com/zelon88/xPress
[2] https://www.honestrepair.net/index.php/2019/03/08/xpress-an-experiment-in-data-compression/ https://www.honestrepair.net/index.php/2019/03/08/xpress-an-...
- mruts 7y agoHave you run it on the competition dataset? What’s the size of the executable + compressed data?
- zelon88 7y agoI'm not sure. Currently the compression variables are somewhat inefficient. I've compressed similar files down to about 17mb using hardcoded variables but I've yet to stumble across one that will reliably compress a variety of data. I was hoping to test it enough to come across patterns that would enable me to develop heuristics, changing the variables according to different input file characteristics. This is simply extremely time consuming. I have a non-open version of a listener for server applications that I've sort of moved my testing over to since I created the client compressor/extractor above.