My name is Leonardo Georgescu, and I am a Jet Propulsion Lab (JPL) summer 2019 intern. The project I am working on is the Axel Rover. Currently, the steepness of the terrain proves to be a challenge for current rover platforms. For example, the exploration of the cryovolcanoes on Titan's moon allow researchers to better understand the moon. Likewise, the flows on Martian slopes are believed to be underground salt water. Finally, lunar pits are a large interest to researchers to explore the lava layers and uncover the truth behind the moon's existence, as well as the use the pits as shelter for astronauts.
Below is a picture of the recurring slope lineae, or RSL. During the warm season, the lines appear and then disappear.
Axel, as pictured below, will descend down the slope and collect samples for analyzing. The Rover has compartments in its wheels for instruments that will sample the RSLs and tell researchers what they are.
During this internship, I will focus on fixing the mechanical and electrical issues, as well as improving the rover for field tests.
After a four hour drive, I arrived in Temple City, the city I am staying in for the duration of my internship. The city, including surrounding Pasadina is very quiet and reserved; a large difference from Las Vegas. It didn't take long for me to get settled into my house. I didn't explore much on my first few days because I was getting ready for the internship.
The first day at JPL was breathtaking. Above is a picture of me in front of the JPL sign at the entrance. Orientation took some time, and immediately after my mentor grabbed me to head over to a meeting. This was the first time that I had the chance to meet everyone I was working with, and learn more about the project itself. After, my mentor took me around the JPL campus, and it was amazing to see the projects they are working on. One of my favorite parts of JPL is the assembly room, where the Mars 2020 Rover is being assembled. I was in shock that I was standing meters away from something that will end up on Mars.
I can say that I started my internship quite well. Unlike the other places I have been to, it didn't take me long to get adjusted at JPL - my group was extremely nice and helpful in getting me ready. Some things that I am working on now are new to me, which makes it very rewarding and fun, and other things I have done in the past.
This week I picked up skills regarding manufacturing some parts. Starting on Monday, I will be finishing all the projects that I started working on last week.
This week, I've learned that it's not about what you know, but how hard you're willing to work to learn. There are times now and in the future where I will be presented with something I don't know, and it's all about the time, and effort I put into learning it. I was amazed at how quickly I was able to learn when there was pressure placed on me. That's a problem that I am currently working on; I tend to procrastinate and become efficient when there's pressure.
Immediately upon arrival there was work for me to do. My mentor contacted me about the job before I arrived at JPL so I could prepare. JPL even makes students complete a project plan before their arrival at JPL so they are much more aware of the projects they will be working on during the 10-week internship as well as getting to know their mentor. I arrived on Tuesday, but had not yet received my JPL laptop, so I spent that day getting familiar with the rover and getting to know the people I would be working with.
The working environment at JPL is different from academic labs. It is much more challenging to find projects to work on at academic labs because they are more research orientated. Even though I am in an R&D lab, at this point, my work does not involve researching.
I am also beginning to see more of the difference between R&D and product development. For example, I am seeing the difference between the Mars 2020 rover and what we are building. R&D focuses more on coming up with the idea and making it work to some extent; it doesn't produce the final product. On the contrary, product development is in charge of taking the product from R&D and making it survive the harsh conditions of Mars, for example. My lab developed the idea of the Axel Rover, and now we are doing field tests to confirm is validate its functionality. If this project is to be approved for future lunar and Mars missions, then it will need to be redesigned to withstand the different environments.
My roommate arrived Saturday, and he asked if I wanted to go to a baseball game that Sunday. I've never been to one before, so I decided to join him. It was a game between the Dodgers and Phillies. It was a very good experience and I enjoyed the game.
At the same time, I also got to learn about him and his work. He is in the process of getting his PhD working on power supplies. He shared some of his experiences and what it meant to be a PhD. One takeaway from him was that I should know why I am going into my PhD if I decide to do it and not just blindly get into the program.
You may be wondering why I posted a picture of a lizard as my photo of the week. This lizard was right outside my lab. I was working on a project with my colleague and we were having difficulties coming up with solutions at the moment. At this point I was in the lab for eight hours, ate my lunch while working, and only took bathroom breaks. My mind was foggy, so I decided to step outside for some fresh air when I saw this lizard. It immediately took my stress away since I was now distracted. Sometimes, it's helpful to get distracted for a few minutes when dealing with frustration.
This lizard also brought back amazing memories of a previous intern at the DASL lab, Jaewon. He was into lizard catching and then releasing them, but had a hard time finding them in Las Vegas. I had a great time with him while he was at the lab, and I even got to see him on my last day in Korea. I hope everything is going well for him.
Things are going very well. My colleague and I finished work ahead of schedule which is an amazing feeling to have before going into the weekend. I am on the 90/80 work schedule, so we were supposed to take Friday off, but because of some projects that were not finished, we ended up staying at work for 12 hours. I didn't mind it at all because we got everything done. After all, we love our work so it doesn't feel like we are working.
Additionally, we received our official work breakdown schedule for the entire internship. We have deadlines to meet, and other project members depend on us finishing our work so this is where the pressure comes from.
This week I began learning more about the lab culture at JPL. My lab is very well structured. The mentor leads the project, but the person above my mentor makes the final decisions. My mentor is in charge of guiding everyone and making sure that deadlines are met. Additionally, my mentor is the one who directly meets with us every week and sometimes comes to check up on us throughout the day. For example, if I'm struggling with a concept, he's there to provide his opinion and talk about why I am stuck. There's much discussion that goes on between lab members which I like because it creates a powerful bond. This is similar to my experience at the KAIST lab because I had Inhwan, a master student who was my mentor, and the PhDs were his mentors. It's a chain of command.
Also, I've noticed that many of these PhDs, including my mentor, do low-level work on top of the high-level work. They could tell my colleague and me to do all the low-level work, but they help us as well so the work can be completed faster. Not to forget that they designed everything from zero. I used to think that PhDs would only do high-level work behind computers, but they can do a wide variety of work ranging from low-level to high-level. Additionally, I was glad to see their openness to give us advise and teach us new things. I think a leader inspires others to do more, and that's the kind of leadership I've seen at JPL.
What amazes me about JPL is the passion that people here have. Most of JPL employers could make more money in other industries such as finance, but they choose to come to JPL because they love their work. The motto of NASA is “for the benefit of all,” meaning that everything we do is to benefit humanity. I can tell immediately that the people at my lab or the thermal engineers working on Mars 2020 are at JPL because they want to do things that no one has done before. This passion resonates to me. There is a fantastic feeling coming to work knowing that everyone else around you is happy. Most JPLers work more than the schedule requires them to work because they love working.
I went to a machine learning speech on Thursday hosted by Dr. Lukas Mandrake. Dr. Mandrake was accepted into college at the age of 13, which is extremely impressive. He is now in charge of the machine learning group at JPL. I can admit that I don't have experience with machine learning, but this speech gave me some critical takeaways. Dr. Mandrake spoke about how machine learning is thrown around and sometimes misused because bad data is used. What is the reason behind this? The people using ML use data without understanding it entirely; it's required that one has the right data. An example he used was how people called ML racist because it didn't select some races for loans. ML is a tool, as he said, so the problem isn't the tool but the person who inputted the data didn't understand the data. Regardless if one knew the specifics of ML or not, the speech was a caution against media and bad data.
My friend from JPL and I hiked up to the Hollywood sign at night. It was a very nice and relaxing hike, but the best part was seeing Los Angeles at night. At the same time, we got to talk about what motivated us to come to JPL. Immigrating to the United States at an early age, she had some difficulties to overcome both culturally and financially, but she was strong enough to get past them and do what she loves. She was very passionate about her project working directly with the Mars 2020 rover and wants to work at JPL after grad school. I enjoyed talking about space robotics and the future of the industry.
Also, special thanks to my lab manager, Dongbin, for coming to visit me and checking up on me.
The main goal of this week was finishing up projects with a quick turnover.
This week I was able to see the assembly of the wheels for the Mars Rover. This is a good place to go take breaks and watch this rover that will end up on Mars be assembled. It's really impressive being so close to it. It's especially amazing seeing the progress being made on it. In one day the Rover's wheels were attached, so progress seems to be going quite fast. It's one thing seeing it online but it's another thing to actually see the Rover in person. This is motivating for us considering that my team is working on future Rovers that could potentially have the same destiny.
This week could be described as very fast paced. The turnaround for these projects is quite amazing. The Tuesday meeting brought new deadlines that we were not previously aware of. I have noticed that to get projects done quickly teams needed to be divided and each person needs to know exactly what needs to be done. Being part of the hardware team means that I have to get the robot ready for the software team to begin testing their algorithms. Sometimes deadlines need to be moved up instead of being pushed back which definitely requires 12 hour+ days.
This week is the most I have done in a single week. In research lab, there is usually more times to think about projects, but here there are time constraints that requires many hours. After this week, I have been thinking about my progress at DASL and realizing that I have taken things quite slow - I was meeting deadlines, but was not finishing projects in a timely matter. When looking at companies such as SpaceX and even Skunkworks, their turnarounds are very fast. Since week one, the turnarounds for this project have been very fast; a lot of small projects had to be accomplished and they got accomplished. It was frustrating and stressful, but the reward definitely outweighed everything else.
Do I like fast turnarounds? Yes, I think they're more excited. The problem I've witnessed is that when projects take too long, it usually ends up slowly dying. It happened with the Personal Tracked Vehicle - I still believe that project could have been successful if there was a plan in place and more work was being done on it. It almost happened with the strain gauges, and definitely with other projects. While they may be stressful at the moment, fast turnarounds are very rewarding. It's about keeping the momentum going. For a fast turnaround to happen, there needs to be clear goals. The “why” has to be answered otherwise it will not work. The reason for many JPL employees being motivated is that they know the reason for everything they do. I know my “why” for being at JPL and working on this project. I know that my hours put into this project will not only help me, but also move the project forward.
Another example of fast turnaround was witnessed at the KAIST Lab. Things were done fast, and sometimes lab members would sleep less than 4 hours. While I am not an advocate of little sleep, they were getting projects done and that really matters. Also, no one is forced to stay at work for a long time - people do it because they are passionate. That is something that is misunderstood with companies even like SpaceX. People talk about how they are overworked. I believe that they are overworking because they want to and are passionate about what they do.
JPL gave me the answer to the “why,” but research labs allow me to explore the “why.” I think that the problem, especially for undergraduates, is that we expect the answer to “why” be given to us when in reality research labs want us to find the meaning behind everything we do. It goes back to the Arizona trip that our lab had. To me, it was very valuable because until then, I didn't really realize what was going on. I was waiting for things to be handed to me. At the time I was working on a thrust stand and thought that the entire project revolved around the thrust stand and that's it. Very little did I know until then that the strain gauges can be used in haptics. The questions that need to be asked are: What can I do with such project? Could this concept be taken somewhere where no one else has taken it before? These questions are the difference between working in industry and research. In industry, the answers are given to you, but in research you are expected to answer them.
One thing I really like about Pasadena is the ability to have so much to do. After six days of working, it's refreshing to go out on different hikes that are not far away. Additionally, I decided to get back into photography. I decided to go to one of the best places for that - Griffith Observatory.
Besides signing up to have my name etched on the Mars 2020 rover not much was done was outside the lab. This is open to the public and JPL will etch all the names on silicon chip. Obviously, the name will be very small but it will still be something interesting.
The reason not much exploring was done was because of the deadlines. JPL workers are on a 9/80 schedule which to my team and I made things more difficult since we had to finish everything by Thursday. Many hours were put into getting the work done, but it did finally end up being complete. It was the biggest sign of relief that late evening when everything worked. As long as things don't end up going completely bad, this week is probably the worst that it will get due to unexpected deadlines.
Besides hardware, my mentor has also tasked me with some later projects involving programming.
Again, the things that matter the most are meeting the deadlines. It was very impressive and we were thankful to have our mentor stay up on Thursday to finish the project. Teamwork has the word team in it meaning that everyone has to participate. I like the ability of the team to come together and help each other when it is needed. I think that this creates a strong bond between lab members; I've experience this type of environment at DASL and at the lab in Korea. Helping others is also a good leadership skill.
One thing different from the lab at JPL compared to DASL is that DASL is generally very clean and organized. There is not much space at JPL, so many teams are working in a small area which means tools can end up not being where they're supposed to be, etcetera. This hasn't impacted my work whatsoever, but it has made it quite interesting since we're very close to each other and are always interacting somehow. At times, we'll even make jokes and tease the other robotic team that is nearby. I think this open space where everyone works together helps bond all of us. What I've noticed during my stay here is how passionate I am for airplane and spacecrafts. I think that I am very inclined to still getting my pilot's license; the only thing that slowed me down was the price of getting one. I think that in the future I should be able to make enough money to get one and fly on the side. Interesting enough, my roommate's friend got his engineering PhD while also getting his pilot's license
I didn't have the time to attend any lectures, but I did end up thinking about my future. With so many different engineering fields, it is difficult to choose where to go. That's one of the biggest issues for me, as I'm going into senior year, is decided where to go from here. At the end of the day, I have to choose what I like to do, but even then there are many choices.
I do want to make it my goal to interact more with others during this internship.Time has gone by very fast, and I've been caught up in work with not enough time to really explore everything there is at JPL.
My free time was spent in Las Vegas. It was nice seeing the lab again, and especially saying goodbye to my lab colleague, Meng, who will be returning to Korea. He was not only a great intern, but a great friend as well. He will be missed.
*Will update with photo once I get the picture from the staff assistant.
Three large events happened this week. The first was the summer intern kick-off with live music and food. We were testing the DuAxel system, and I only got to attend the last 15 minutes, but there was still some food left, and I got to talk to my friends. Later that evening the Axel Team celebrated the progress of the Rover. It was a great time to speak to my team outside of the lab. I ended up talking with the supervisor of the Robotic Mobility Group about the reason for coming to JPL and how I like it so far. The last event of the week was the Robotics Group picnic in the park. There was food, games, and the best part was getting to interact with others in my section that I have never met before. I think that it's time for DASL team members to go out and play some sports, or even go hiking - some activity that could be done more often that would help bring us together.
Many side projects were being completed while testing was being done on the system. This week was mostly designing components that would help with the functionality of the Rover. Outside of the lab, I went through all the ROS tutorials to familiarize myself with the system. Not only would it be beneficial while at JPL, but it is also helpful when I come back to DASL. I will continue working on the weekends to learn more programming.
Being able to interact with other JPL members more this week, I learned what it takes to get a project approved and how the cost is structured. These space missions are costly because many skilled laborers come together to ensure that the project does not fail. Most of the money goes to labor, of course, and the rest goes to the high precision components.
I seem to notice at JPL that everyone has a specific project that they are working on. Compared to the places I have been before, JPL employees have tasks, such as, for example, designing a power supply for some mission, or working only with path planning. As a mechanical engineer, it is expected that I am familiar with CAD programs, so most likely, I will end up on a project dealing with designing and testing parts. I came to JPL thinking that only a Ph.D. can get a job here, but I'm seeing that depending on what one wants to do the degree level does not matter. For example, half of the robotics group is made up of Masters, and the other half is Ph.D. There are some with a bachelor's degree, and I ended up meeting one mechanical engineer who is brilliant at designing and received his bachelor's. I'm seeing that JPL focuses more on the experience that the person has, and contrary to a popular misconception that JPL recruits only from top schools, there are people from all over the place.
Some friends from JPL and I went down to the crowded and famous Santa Monica Pier. This was the third time I've been there, but I'll go again as long as I'm with friends. We ended up talking about the different projects going on at JPL, getting to share stories. One intern previously was an intern at Langley and was telling me about the flight research they do, which seems very interesting. Note, that this conversation came about after I correctly identified the plane that took off from LAX. People always give me the same reaction when I identify planes, but I remind them that I spent my childhood plane watching, and that's the reason I haven't watched most of the Disney or Marvel movies.
This week I met Sunggoo and Hanseob, JPL interns working on the DARPA subterranean challenge. Last year during this time, I was in the lab with them at KAIST under Professor Shim. Now I'm thinking to myself what a coincidence it is to see them again but at a different lab. I was very excited to see them and learn about the projects they are working on; looking forward to spending more time with them even though they are busy.
We only had to show up two days for work even though we decided to show up more to finish assembling the second part of the rover after the design change. We were continuing working on things that we have already started working on last week, and we need to finish them by the end of the next coming week.
I spent last weekend getting familiar with ROS, and this week, I took the initiative actually to get familiar by working with ROS on the Rover. I completed a little project nonetheless, but it did help me. One of my goals this summer is to pick up on some programming. I think it has been a little challenging by not being immersed in a project that is programming heavy and having to deal with the frustrations.
I've learned that spending every hour at the lab, for seven days a week is not the best way to go about it. I'm also not saying that I should cut down on my work, but instead be smart about how I work because I've found myself wasting time.
I have the mentality, which I believe is wrong, that if I can't figure something out, I will sit there and not leave until I finish figuring out what I have to. I think that when I run into a problem, I have to take a break and work or do something that is not related to clear my mind. Being frustrated and trying to solve the problem has only led me to be even more frustrated, and the cycle repeats itself. Another reason why I'm all about getting my pilot's license is so I can fly and take a break, or even exercise. It's not about doing less work, but doing the same amount of work more efficiently. I've come to this conclusion based on my experience and also seeing how the PhDs at the lab deal with problems.
Fourth of July, my roommate, and another intern hiked the mountain to see the LA fireworks, which were terrific. The other intern has some friends who recently got hired at JPL and wanted to help me connect to them since they do flight controls. Besides, I did some studying and started reading an exciting book called the “Vital Question” by Nick Lane. A fascinating book, but takes a long time to read since I don't know biology.
On Sunday, my roommate invited me to some Ultimate Frisbee Games on the beach. I met different people from LA, and also another JPL engineer at the games, and all three of us will have lunch at work to get to know each other better. In the morning, we watched the women's soccer team, and I was very proud of seeing the team win the game. Afterward, the games began, and we played for about 4 hours straight - I'm sunburnt and exhausted, but it was an excellent way to end the weekend before starting work again tomorrow.
This week we went to see the Apollo 11 immersive show since this year marks the 50th anniversary. I went with Nathan, a colleague working on Axel with me. The show was explaining the life of an engineer and what he had to go through to make this launch possible. It was very motivating because it shows that humans can achieve great things if we are determined to get it done. People worked hard, people got divorves, and people died to make the lunar landing possible. As Elon Musk said, “When something is important enough, you do it even if the odds are not in your favor.”
It was a very successful week. We finished the largest project on time, and now what remains is smaller projects that will contribute to the robustness of the rover, but the functionality of the rover does not depend on it. The hours put into getting the main project done completely paid off. The field test is approaching which is very exciting.
Additionally, I met with a Senior Research Scientist working on Aerial Robotics. We spoke for some time about the future of the drone industry, and how we can collaborate in the future on projects. There are many problems in the drone industry that need to be tackled before drones can be a vital part of our lives.
I need to ask more questions. Speaking with the Research Scientist was very valuable; many of the projects he suggested I left with excitement as there are many areas where I can make an impact in the industry. I think a large issue is that I have not taken initiative on any project. I may have mentioned this earlier, but as I'm speaking with students and senior researchers they are taking initiatives. I also spoke to a PhD candidate from University of Michigan who works on bio-inspired manipulators. Like I was previously saying, he has taken initiative with his projects and that launched him in the industry. As of right now, I am working on many different projects, but I have failed to fully take a project to the next step.
My friends from JPL and I went down to the beach in Malibu; Shaq has a house there. Great architecture and wonderful scenery especially during sunset. I can definitely say that I am a big fan of everything outside of LA, just not the city itself.
This is the car to one of the research scientists that goes out to the desert land he bought to fly and launch different vehicles. I got invited to a balloon launch on August 2nd that I am very excited to attend. The reason I took a picture of this car is because he lets one of his interns maintain and modify it for fun - sounds like a fun project.
It was another great week at work, finishing the hardware changes and instrument implementation before some tests on Monday and Tuesday. Everything worked! I had a lot of fun working with the instruments and getting data. Also, I was very happy to find out that I will be in charge of operating the instruments during the primary test in August.
Reflecting on the skills I have learned during this internship are: design in Solidworks, 3D printing, electrical diagram, and operations of a Rover. In all, I have learned how to do things the right now and that is why the PTV will forever be a disappointed for me.
I have been neglecting to look at the thrust stand and meeting with people at JPL that could guide me. This is something that I need to do before my internship here ends. It goes with the fact that I am lost when it comes to what I want to do. I have spent some time learning a little of many things, but I haven't become an expert in anything. I guess this is alright for undergraduates, but I am beginning to worry. Since I have a year and a half left, I don't know what my main focus has been during my undergraduate degree. I feel like I have touched many topics, but I haven't picked one up yet. Simple said I haven't taken the initiative on anything.
It has also crossed my mind about whether graduate school is really for me. I know that I do want to further my education, but I do not feel prepared for it. Graduate school would work out better for me if I could somehow mix flying and learning. I think I will quite busy this year, deciding what I want to pursue.
My car decided to stall upon starting it. I figured out it was the mass airflow sensor, so I changed it myself. I then realized that I enjoy when things go wrong with my car because it allows me to fix it, which I find fun to do.
I didn't do anything fun besides some side work since I am not allowed to be at JPL during the weekends. I spoke with Dongbin this weekend to get me started with ROS and OpenCV. The goal was to move the turtle in turtlesim using the motions captured from my laptop camera — a great project to work on the side when there is time. Additionally, I looked at a journal from JPL regarding thrust stands. I have concluded that my thrust stand needs to be redesigned because it does not account for many variables.
I attended a talk hosting three engineers that worked on the Apollo 11. Laurence Mizzell worked on a portable battery powered unit that would allow the monitoring of glitches during testing. Shelby Jacobs worked on the famous camera that recorded the film of the separation, and lastly Percy Brown worked on the Rocketdyne F-1, and other engines. It was very interesting hearing how engineering was done back in the days; they didn't seem to care so much about safety. Mr. Brown had to climb inside the engine as they were getting ready to fire it to ensure that everything was alright. Being at JPL, I've gotten insight on what it takes to launch space robots and satellites, but things are very different when we are sending human life. This talk was also a little disappointing because many engineers have gone unnoticed. People tend to talk about the astronauts as heroes, and they are heroes, but people rarely talk about the engineers that made it all happen. I assume things were much more difficult back then. Everything was done on paper, and Google wasn't available to them. It's interesting to me hearing what other engineers how engineers back in the day performed their jobs. it for fun - sounds like a fun project.
Thrust Stand: I want to start with the thrust stand because I think reading papers I've made some interesting discoveries. I'll try to keep this short. The fact that I was getting a linear curve meant that my strain gauges, amplification, and DAQ are working well; simply, my method of data acquisition is correct. Unfortunately, this does not mean that there are not errors. It's very interesting because if there is error in the system, then there will be error in the calibration and when the motor is running. What I may be getting is a false-positive result.
The issue I am having with the thrust stand it seeing where to take it. There are many ways of designing a thrust stand which makes it hard to settle down on one. The most important thing to consider is that the force vector during calibration and when the motor is mounted should be the same. For this reason, the deflection has to occur parallel to the thrust vector. In my case it is not because I am getting large angular deflections, or rotational deflection. As shown below, I need parallel linkages. The image below was taken from the journal titled “Recommended Practices in Thrust Measurements,” and some of the people that wrote it work or have worked at JPL. When we are dealing with such small measurements, these mistakes can affect everything
What changes will I make? I think I am still in Version 1.0, so I can make a few changes without having to redo the entire project. The image below shows the basics of what I will work on once I get back to the lab. I will target the inverted pendulum thrust stand. Additionally, I'll have a Photodetector that will record the RPM. It sends out the signal in voltages and then I will be able to read that. Vibration being a big issue with my current platform needs to be addressed by having some dampers. I was going to draw it in CAD but I ran into a plethora of issues with my car.
I have not been able to meet with someone regarding the thrust stand. I'm waiting for a response, and it has been very busy getting the Rover ready for field tests. I've been putting in many hours this week, so I haven't been fully proactive with connecting with someone regarding the thrust stand. I will also mention it to my mentor who could help connect with someone on campus.
My work has been completed for week. All the designs have been finalized, sometimes after multiple attempts, and changes. Now, I am waiting for the parts to arrive to put them on the Rover. I am a little nervous and hopefully all the parts are working.
It's easy to get frustrated at problems, but I should start looking at them as learning opportunities. My car decided to stall during driving. I was mad because the last thing I wanted to do was deal with it. Fortunately, I was able to repair it after buying some tools and going for it. Now, my car is operational again and I was very happy. Yes, someone could say I “wasted” a lot of time with it while I could have done something more productive, but I disagree. I've learned much about air flow through the car and the sensor involved. Most importantly, I've learned how to problem solve. In engineering we deal with systems that will fail, and we need to know how to calmly approach the problem. I'm learning that every obstacle is an opportunity for me to learn.
My mentor told me Friday night that this internship will forever change the way I engineer things. He is right! I wasn't detail-orientated when I came to JPL. At my lab, I would just put things together and call it a day. The idea was to “just make it work.” It does not work! I've had days at JPL that were very frustrating, especially this week, because I've had to resubmit many revisions of designs. Everything has to be accounted for. When I built the thrust stand or the PTV I went right into it without planning. I just put things together and hoped they worked. That's not the engineer I want to be. I've failed to document things in the lab; i've failed to design things correctly. I appreciate my mentor for being tough on me because it really taught me valuable skills. I need to cut the assumptions. The right way to do it is to take as much into consideration as possible, draw it in CAD, simulate it, calculate the numbers, prototype it, revise it, and do it over and over until it's close to perfect. It takes time, but things need to be done right. My mentor extended his undergraduate to fit in many different classes. I want to do similar to what he did. His main focus at the beginning was mechanical engineering and getting to really know the fundamentals of designing and building things. Then, he went into software and electrical which broadened his robotics knowledge. My time at JPL was spent heavily learning the fundamentals of mechanical engineering. After, if I focus on programming, which I am behind on, then I can create two very strong skillsets.
I went to my mentor's house since he was hosting a going away party for an intern who has been here for an entire year. It was amazing getting to spend time outside of the lab with everyone from the lab. We played board games until midnight. I think it's something that I want to bring back at DASL so we can strengthen our team.
Most of my free time was spent debugging and fixing my car. The time I had in between was spent researching methods of improving the thrust stand.
This was the week that I was most afraid of this entire summer. The week leading up to either competitions or field tests are notorious for lack of sleep, high stress, and many work hours. Exactly what I was afraid of happening did happen. Unfortunately, I was not able to do anything outside of the lab this week, not even meet with people or get much sleep for that matter.
The most important work parts of the rover were completed before the field test; everyone rushed to get their work done last minute. The most important thing was that everything was done - and I could sleep very well during the two hours of sleep I got on Sunday before the field test on Monday knowing that things have a chance of going well. I don't think I've ever been more under pressure than this week, and I can only imagine what was going on during the DARPA competition.
I feel as if with all the planning in the world, the weeks leading to a competition or field tests are always going to be stressful. I had to print 3d print a nylon part which was located in the building housing the DARPA terrain team, and they were close to the competition. The room was complete chaos - people were everywhere, everyone seemed to be stressed out, some I spoke with pulled multiple all nighters. I think it is during these moments that teams bond the most; it is these tough moments that unite the group. When you're on a team, and everyone is pulling those all-nighters then you start being there for one another.
You can say that better planning prevents these weeks from happening, but I would say that they're bound to happen either way. Even with perfect planning, there are things along the way that will throw the schedule off course. These tough days will happen but you have to keep reminding yourself that shortly they will be over.
The only thing I did during my free time was sleep and eat. I also did not get to attend the balloon launch I got invited to which made me a little sad;
This is a picture of me with Axel 3B, the one designed to explore the RSL's on Mars. As seen in the picture, I am sleep deprived, but nonetheless it was a very fun weekend. This picture was taken on the slope after driving autonomously. It has been very excited being part of this project and being able to contribute to its success. I hope that this project will continue on and become a mission.
My job this week was mostly a “rover paramedic” as I was called. When something went wrong, my mentor and I would go debug the issues. The goal was to get it ready fast because these field tests cost a lot of money per hour. The four days of the field test were very busy, but the last day was the least busy for me since the software engineers took over and the rover had no issue.
Also, it was great being part of the instrument deployment team, getting data from the instruments. I was operating the computer, setting different parameters for the instrument software, and then taking measurements. In this process, I learned a lot about how dielectric probes and spectrometers work.
Again, it was a tough week being out in the desert the entire day, eating poorly, and not sleeping much, but I think it was very rewarding. Most importantly, I was very excited to see this turn into a successful field test. We got past all the problems, and made it all work out.
As they say, hard work pays off. Nothing was exciting as sitting back and realizing that everything went well and all the work paid off. Even though I still have two weeks left of my internship, this field test was a great way to put an end to my days at JPL, and I hope I get to have more awesome opportunities such as this in the future.
Recover! I spent the weekend cleaning and recovering from the past weeks. I spent some time on python, talking with Dylan about the senior design project, and talking to my startup team from JPL about getting things going. I think this year will be a test for me, but I will make it a successful year.
It was mentor appreciation day in which mentor and interns would spend some time talking while enjoying the music and food. In the picture from left to right is Prashant Iyer and Issa Nesnas. Prashant is a Caltech alumna and works at India Space Research and Organization. Dr. Issa Nesnas is the principal investigator for Axel and has been working with the rover for over 20 years. It's great hearing the stories from people who are extremely dedicated to their projects.
This week was a little slower than usual because it was after the field test and we were all recovering. I finished all the projects I had for this internship and started writing my final report. Also, assisted in Prashant while he was testing his new algorithm for the DuAxel/Axel system. He was kind of nice to walk me through the code and teach me a few things about ROS. Also, excited and grateful to be a part of the beginnings of a startup with a JPL research scientist and other interns. I think this experience will be nonetheless challenging but also rewarding in terms of what I learn from it. It's also great being part of a team that shares the same passion - flying.
I think this has been the most productive summer so far. Got a lot of fundamentals down and learned the lab culture very well. I finally got the hang of how things work at JPL, and it's unfortunate that this will be my last week. I will miss the team and the rover as well. The team has been very supportive and they spend time with interns guiding them along the way.
I've spent a lot of time this week reflecting and trying to understand what myself. There are many projects out there that are very exciting to me, but it's time that I take the initiative on one. The first step is to return back to my home, DASL, and bring back everything I have learned at JPL.
Prashant and I had dinner at an Indian restaurant. He was explaining to me his position at ISRO and what the agency is all about. Prashant even invited me to India and offered to give me a tour of ISRO; maybe it's time I really do take a trip. I enjoy getting to know people from other places and what they do.
I made sure I visited the Science Museum and saw the Endeavour Shuttle before returning back home. You see this shuttle on youtube or on TV, but it looks much smaller than it does in reality. For me, it was also exciting to be so close to a vehicle that has been in space.