This is a detailed blog post regarding my first week of code.

My work involves adding a label feature to tag the datasets such that when I train multiple models on the same datasets i'm able to distinguish between them which would be very helpful while training multiple models simultaneously.

As a stepping stone, my mentor asked me to implement it for a specific type of source, and hence JSONSource was chosen. The codebase has grown a lot since i wrote my proposal so most of the time was spent in understanding the workflow so that i can analyse where the changes have to be made. After trying to understand the code by giving so many print statements in between lines, finally I got an idea of how i'm supposed to achieve my goal.

Now that I know what changes have to be done, the challenge was in not only making those changes but also testing it. While making the changes, there have been instances where unexpectedly we see some whacky behaviour. This lead to code changes in places we didn't expect in the beginning. Thanks to this, now we have tightened up few loose ends. After making the necessary changes, my mentor and I worked on testing it.

Initial testing was a failure and there were so many unexpected errors. Since the changes were done in a function that dumps the data into a file, all the tests that were directly or indirectly using this were failing. We figured out everything expect for JSONDecodeError that was occuring when we are trying to do json.load() in dump_fd() in JSONSource.

We somehow figured why this error occured and fixed it in the future week. See the next blog post for updates on this!

In the first week of coding, I worked on implementing a part of the feature in the project. More details on what I'll be working on throughout GSoC can be found here.

What did I do this week?

I submitted a PR on the part I was working on. My mentor reviewed my code and requested changes. I have modified according to it. After that, we are working on debugging the errors that occur while running tests.

What is coming up next?

I'll be working on debugging and add few more tests for this feature. If I'm able to finish this before next weekend, I'll work on implementing the same feature for a different type of FileSource.

Did you get stuck anywhere?

Currently, my mentor and I are working on debugging the errors. It shows some whacky behaviour so we are trying to fix it.

Hola Amigos! I'm Sudharsana K J L from Tamil Nadu, India. I'll be contributing to DFFML. To know more about this cool project visit here.

What did I do this week?

During the community bonding period, the timing for our weekly catch up meetings was decided and I've had two calls with my mentor already in which we discussed about the project and about my proposal and how it could be achieved. A lot of things have changed in the code base since i wrote the proposal, so i spent my time this week trying to understand the code changes. I've also moved to a new house, so things have been pretty tight with the packing and unpacking. During the sessions with my mentor, he explained me and my fellow GSoC'er Yash about the new additions in the code and how it helps improve DFFML. The past week, I've been trying to understand and figure out how to add the feature I'm gonna work on.

What is coming up next?

With the coding session starting next week, I'll be working on adding the initial part of the feature. This will help me get a clear idea of how to proceed with the other features I'm hoping to add.

Did you get stuck anywhere?

I was stuck on understanding the new code and the working of few classes but my mentor is very active and responds to my silly queries patiently and helps me in getting to know the project better.