Thursday, August 18

Pardon the silence. I've been driving back to Seattle this week so have been bad with communication. This week I've been polishing all of my code for the final submission deadline which is approaching and now everything is done! All of my final code, in addition to some sample bitmap files and query files, can be found at https://github.com/aingerson/GSoC_2016_Compressor. It's been a great summer and I am extremely satisfied with all of the work I have done on this. Many thanks for the support!

Wednesday, August 10

As I mentioned in a previous post, I'm driving to Seattle so my posts this week are going to be rather spotty but I'm currently developing tests to test the capabilities of VAL versus WAH.

Monday, August 8

Preparing my code for the final submission. All of the code is pretty much good to go. I'm driving back to Seattle on Wednesday so I won't be able to code for the second half of the week which is fine because the coding is done. But during my driving I will be coming up with tests to run in order to evaluate the performance of the new algorithm against the old. 

Thursday, August 4

Letting my computer recover from yesterday's adventure. I went to the Apple Store because of the advice Bart gave me (thank, you, Bart!) and they took it apart and could not find any trace of liquid damage so that's very good news!!

Wednesday, August 3

I decided that I should design and run some tests to evaluate the performance of VAL against WAH so I was working on that today when I spilled coffee all over my computer. Needless to say today I was panicking a bit but managed to keep my cool. All of the code is backed up though and my computer seems to work perfectly fine so I'm not terribly concerned. But that was definitely the thrill of the day!

Tuesday, August 2

Finished commenting and organizing my code today. Haven't heard from David yet so I'll teach it again tomorrow. 

Monday, August 1

I messaged David on Friday to let him know I have finished coding VAL and to ask him what he thinks will be the best way to test the code will be but haven't heard anything from him so I spent the day commenting and cleaning my code. I'll message him again tomorrow.