[Week 09] — Cadair is back!
This blog post deals with the entry of tasks that I did for the 9th week for the project under Google Summer of Code 2019.
Crawling through this week’s targets
The target for this week was really clear for me — Get the bug fix PR merged, and hop onto something else. Sounds simple? Nah!
In spite of dedicating a week, I was still not able to get the bug-fix completed, as it later led to opening to a can of worms(bugs)!
Earlier, I had finally made some changes to the plotting code, and voila it was working. Note that I was able to understand most of the plotting semantics, and I was mostly convinced about my bug fix that fixed the two failing tests. This was a moment of sigh for me, as I finally solved the issue which was stagnant for a couple of months since I made the PR.
Striking the reality
However, the reality struck, as I was getting my code merged, my mentor @DanRyanIrish, reviewed the code and tried out a few examples from the docs( which in hindsight I should have done that!) which were failing drastically. This was quite scary for me as it seemed that all those week’s effort was gone into waste, and I was back to square one.
After recovering from the initial shock, I decided to go through the issues that Dan was having, and on close inspection, it was seeming to me that those were something which wasn’t something from my code. On trying the doc examples, the examples were breaking in an un-premeditated way, which was shocking and at the same time, a bit reassuring that my rewrite wasn’t creating an issue which was present earlier.
I had a discussion with Dan and he asked me to file an issue, as it was quite different from the issue which I was solving.
Cadair is back!
@Cadair is the name of my other mentor, Stuart Mumford. He went for few weeks of excursion, and I was quite happy that he was back for SunPy. I had been working closely with him for the past few months, so I was really waiting for him to arrive back.
I discussed my issue with @Cadair and he suggested that we should hold a telecon, and I should get some insights about plotting from Dan. This was quite reassuring, as it can pretty become scary on managing stuff all alone.
@DanRyanIrish has been quite busy, so it was really difficult for him to be active all the time. With Cadair back in the scene, I discussed with him about stuff that needs to be worked upon. We decided to skip out the animate-1D plotting part of NDCube until Dan is free, and start with the 2D plotting.
Back to track
My previous bug isn’t fixed, but I have moved to tackle the 2D and 3D plotting. I have wasted around 3–4 days playing the waiting game, as the period between pushing the PR and getting reviewed took some time, and I was clueless about the progress. In the hindsight, I should have started with another task, and rather than playing the waiting game.
I have made two PRs for 2D and 3D plotting, and those are still quite basic ones, but I will add more tests as I face any sort of issues. Currently, at the time of writing this post, I have incurred a bug, which I am discussing now 😛.
Tasks for the next week
For the next week, I have a telecon arranged with my mentors on a Wednesday, so hopefully, I can get insights about the plotting code. I also plan to work out the present bug that I am facing, so that would be next week’s priority tasks.
Link to my previous post
- [Week 08] — Gearing up for the plotting — II — Link
