Author: Francis Palustre, Email: palusf1@unlv.nevada.edu
Date Last Modified: 06/26/2024

This week was one of the more busier weeks in terms of team goals. Meaning, there is a lot more people who came to the faculty, and one of them is Ryan (a different one). If I recall correctly, he finished his masters in mathematics, but never did his PHD because of our common hatred of derivation. He showed us what math can do during our discussion and how much math is involved with what we can do, and it is quite interesting.

Unlike the lab, in which everyone does their own thing, NNSS has a clear objective to do. I know that DASL can have that, but the way I see it is that we combine ideas to make tangible, on the other hand, what we are doing is one part of the total idea. This was quite apparent as this week we had a full team meeting, which is, funnily enough, rare.

To be honest, I don't know what I can reflect myself thoughtfully as I spent my week learning how to setup launch files and urdf's. If there is anything, I suppose it's taking the time to understand other people's work. Maybe it's me seeing math being used in a while, or me wanting to read other people's code, but I don't typically think about other people's work, but it is useful when you are working in a team.

I have finally been able to code something! Well, it is not the “make a program” type of coding that I am used to, but rather, it's a launch file for ROS2 and xml. The launch file weren't that bad to do, since it's Python and it's supposed to be easier when compared ROS1's method, which, it is. On the other hand, xml, for creating urdf's is a big pain to deal with. It makes sense, but doesn't at the same time and I think for me, it is mainly the syntax and how everything is laid out. I don't know why, but it is difficult to process when compared to other programming languages.