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

Similarly with last week, we mainly worked online, so I didn't meet any new people this week. I couldn't attend the WishCon event because I had an appointment around where it started, so I couldn't really meet anyone new.

Recently, I been talking with Nathan more because of the current project we are currently working on in DASL and how nice it is to have someone in your vicinity to communicate with. A few days ago, he mentioned to me that there were other interns besides us two, but we never even saw them because they mainly worked remote. Knowing how restrictive working at RSL is, it makes sense, but it is mind boggling to me that we didn't even know they existed until WishCon, and in my case, Nathan telling me about them. So, I started to see the value in working in a team that someone is within walking distance to discuss current projects.

This is not as much as a valuable lesson compared to previous weeks, but something that I should consider are hardware issues. Personally, I try to avoid blaming any sort of hardware issues when it comes to whatever project I am working on because I always think it is some coding problem, but I would need to start considering that hardware can be a potentially issue rather than a last resort one.

For this week, I am collaborating with Nathan in combining the real-world lidar data with my URDF model in RVIZ, so they can be in sync with one another. Honestly, it is one of the easier projects I was assigned in, but sometimes it doesn't make sense on why we have certain problems because logically, it would create a clear chain, or linked-list structure in the xml code, but RVIZ would say otherwise. So, while it is one of the easier projects, it is also one of the more confusing ones.