Summary Report
Late nights, excitement and learning are how I would describe the GSoC period in a few words. These past two months have been a lot of fun, from starting off...
I made more progress with the documentation and some other auxillary bug fixes this week.
Continuing on last week’s images, this week I wrote the basic documentation for all of the blocks in Visual Circuit.
It was done by adding a docstring to the main()
function of the Python file. Pdoc then automatically reads it and displays it in an HTML format.
We had a debugging session in the meet this week, however we couldn’t find an efficient way to perfect the execution of the Vaccum Cleaner agent.
I discovered a bug that while saving blocks. Sometimes the height and width of the code blocks are saved as very small values roughly to the tune of 14-19px. So when loading a saved design again, the code block usually opens with a very small size. I pushed a commit fixing this issue in the existing blocks by changing their height and width values.
However, the larger symptom of why this bug occurs still remains at large.
Aside from this I pushed a feature that added the .vc3
configuration file to the built application as well. This is helpful as we often forget to save the configuration file while after building the application. Later if we want to make structural changes to our design, we will require this file. Hence bundling it along with the built application is more convenient for users.
Late nights, excitement and learning are how I would describe the GSoC period in a few words. These past two months have been a lot of fun, from starting off...
Going by the suggestions of my mentors, I spent this week working on the documentation of the blocks and some updates to my blog.
This week I looked into MultiProcessing Conditions and finished the video of the FSM.
This week saw the completion of the FSM video and the solution to the block size bug.
I made more progress with the documentation and some other auxillary bug fixes this week.
Another pretty busy week for me personally. This led to a bit of slowdown in the work done. However I started with the documentation editing through Jinja an...
This week was quite hectic for me. My college started offline after a while, due to travelling and a few other events the time I could spend on Visual Circui...
This was a week where I started to work on the Finite State Machine that I had mentioned in my proposal.
This week marked a focus on completing the remaining PRs from last week. I also finished adding a new IMU block and worked on general share() and read() func...
This week I finally finished the remaining templates from last week. I also managed to upload my created videos to the JdeRobot YouTube Channel.
This week was about identifying and solving some bugs I had noticed during usage of the tool. I also started with the work template updation.
This week marked the official beginning of the coding period. Going by last week’s set goals I started on the video creation part first and foremost.
This was the last week of community bonding, however due to other commitments in college I had a hard time working on Visual Circuit.
In my previous posts I had highlighted the challenges I faced while installing Jde Drones and getting code running on it. Next after these steps was to solve...
After I got the drones running now it was time to actually write the code to solve some exercises. The goal for this week of the GSoC period was to get 1-2 a...
Getting started with my GSoC period, one of my goals during the project was to make drone applications using Visual Circuit. JdeRobot’s Academy already has s...