| Next revision | Previous revision |
| nnss6_palustre_francis [2024/07/12 12:33] – created fpalustre | nnss6_palustre_francis [2024/07/13 17:53] (current) – [Technical Projects] fpalustre |
|---|
| **Author:** Francis Palustre, Email: <palusf1@unlv.nevada.edu> | **Author:** Francis Palustre, Email: <palusf1@unlv.nevada.edu> |
| \\ | \\ |
| **Date Last Modified:** 07/12/2024 | **Date Last Modified:** 07/13/2024 |
| \\ | \\ |
| ===== Week 6 ===== | ===== Week 6 ===== |
| \\ | \\ |
| ==== Cultural Insight ==== | ==== Cultural Insight ==== |
| 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. | I felt like a huge insight that I didn't really notice until now is the idea of a 9-5 work schedule. Personally, I am a big fan of the way DASL does it work hours, being whenever you come in and show your work. Because to me, it doesn't feel like work half the time because it slightly motivates me to come in, since I don't a schedule to follow through |
| \\ | \\ |
| ==== Self Lesson ==== | ==== Self Lesson ==== |
| 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, a huge lesson that was made even more clear for me is that I need to start thinking as team. It's typically quite hard for me to work in a team because of my reliance towards other people, but something I didn't quite consider is having a timed schedule. I have been so used to this skunk-work time setup that I have less considerations of when I should work. While I still clock out around 5, I typically start between 9-10, meaning I don't get my 40 hours a week. This is only a huge lesson because I had a lecture about it from higher-ups... |
| \\ | \\ |
| ==== Technical Projects ===== | ==== Technical Projects ===== |
| 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. | For this week, despite my ever increasing, yet now steady disdain towards URDF's for ROS2...no, I still hate it. I actually only enjoyed on Thursday because I was able to relate the transform points of my models to a simulation test that was done earlier that week. Meaning, that when a separate model moves, lets say a person, my models will follow that person's every translation or rotation they make. Now, I said the points, not the models yet, so that is my goal for the next week and I hope I get it done no later than Tuesday because this is starting to become boring work to me. |
