Now that the Google Summer of Code 2016 (yes, I wrote that whole thing instead of GSoC ’16) has officially started, I don’t know what to do.
😐 I really don’t. 😐
Well, I had a lot of plans (Really? I wrote those things? Wow…) for this period in my proposal but they just seem trivial now, reading code and all that stuff. Thanks to my work before the proposal submission I have a good idea on exactly what to do and how to do it.
So most of the Community Bonding period went by and I did nothing. Literally, nothing.
So, coming back to topic ( not really 🙂 ), there were approximately 10 days left and I decided to do code up some new feature and after a meeting with Cadair we decided that I should try to implement a VSO ( go here ) caching mechanism which would save bandwidth and hence save time ( a lot of time ).
The problem was that currently the SunPy database module had a cache which did not download files only if any query was exactly identical to a previous query ( for which files were downloaded successfully ). So if there were 2 queries that were slightly different but had a large overlap, all files would be downloaded again for the second query.
So I did manage to accomplish that feature in the end (easy to say). As you may have guessed by now (duh!), an additional advantage was that users can now download files for a large query and then can peacefully 😀 work on any subset of that query. Yes, highly productive work.
You can have a look at it here : VSO query result block level caching
I also had a look at my previous pending Pull Requests and made some changes according to the review comments.
And after that, well, the Community Bonding period ended. What did you expect, an alien invasion?