As the model became more complex, another challenge was structuring the code so that it could support repeated analyses without duplicating calculations. I converted the original calculation script into a function and built separate trade-study programs around it. This allowed me to systematically vary chamber pressure, nozzle expansion ratio, and altitude while generating performance maps and 3D surfaces, which helps to visualize the complexity of balancing all these variables. I also developed a standard-atmosphere model so that ambient pressure could be calculated as a function of altitude rather than manually specified.

To check how accurate my model was, I validated it against NASA's analytical equations and then compared it with experimental results from a NASA high-area-ratio rocket nozzle study. For a 1025:1 expansion-ratio nozzle, my model predicted a vacuum thrust coefficient of 2.069, compared with NASA's experimental range of 1.92–2.02, placing the prediction approximately 2.4% above the upper experimental bound. 

From this project, I learned about the importance of using effective models to predict data about rocket launches, and that models are almost never entirely accurate to reality, and must be taken into consideration when using models for decisions.

Design Process: Had a lot of issues when navigating the Teamcenter UI while trying to upload the parts from NX, it was a pain trying to figure it out. The submission had to be done through teamcenter, and the feedback provided was also on the teamcenter submission. Once I had it down it became a natural part of my workflow. I also struggled a lot with the constraints, as some constraints would throw an error at you, and I had to undo the work, redesign the part until it fit properly. 

Takeaways: Ultimately I learned to properly design the part you are making before beggining any sort of CAD. I also learned the importance of PLM and managing your parts properly on an external software like Teamcenter.

I disliked the previous way of managing calls, where user requests were put into a spreadsheet, where we would need to manually call the person, then remove them from the spreadsheet every time. It was a pain, so I brought up this idea to my supervisor, and he allowed me and a more html literate employee to construct a basic website that would store, automatically dial, and remove user requests when comlpeted. Significantly cut down time for each call, and allowed each employee to accept more requests per day.