First week of GSoC: Going down several rabbit holes

Published: 06/02/2019

1. What did you do this week?

This week was characterized by many different smaller tasks, such as:

  1. improvements to documentation,
  2. fixing of bugs (typo-bugs),
  3. speeding up continuous integration through caching,
  4. opening issues to discuss potential APIs for analysis pipelines,
  5. ... and some more

To track my progress in GSoC, I have made a repository: where I host a changelog file that contains each issue/pr/task that I have worked on, divided by weeks and days.

For my overall project, the most important work was probably opening an issue to discuss potential APIs for analysis pipelines. I suggested a JSON-file centered approach, and Mainak (my mentor) pointed me to several existing solutions. In our chat on Gitter we later agreed to target the mne-study-template and improving it, before making an attempt to program a new pipeline from scratch.

2. What is coming up next?

Next week I will also travel to Rome for the OHBM conference, where I will meet Mainak and Alex who are mentoring me during this GSoC.

3. Did you get stuck anywhere?

I do not feel like I "got stuck" with anything in particular, but neither did I make a good "first step" with my project. As indicated in the title of this post, I always started to do something, and then got sidetracked by minor issues that I first wanted to fix. This ended up being a big time investment for each fix. It feels good to fix minor issues, but it should not distract me from the overall goal of the GSoC :-)