Flight Simulation Software Exploration Design Doc

Owned by Joel Godard
Last updated: Oct 28, 2022
3 min read

Background and Motivation

The team has previously mainly used openrocket for flight simulation but there may be better software that more correctly simulates our specific rocket trajectory, While ideas have been thrown around in the past no one has done an in depth study of other software and advantages/disadvantages of them.

Project Description, Requirements and Scope

Description:

The purpose of this project is to research various flight simulation software, namely RASAero and determine what is most useful and accurate for the team moving forward.

Work that should be done:

Sequential Tasks:

  1. Research RASAero, Rocksim and RocketPy to determine the overall advantages and disadvantages of each. Use data and solid reasoning to decide on one or two to pursue further.

    1. Make a simple rocket in the software chosen to learn how to use the software either after or in late stages of the above step. 

  2. Make a rough model of our rocket in the one or two programs of choice (potentially using a COTS motor if this simplifies the process)

    1. If it is feasible, model our engine in the program/s of choice to be able to directly compare the OpenRocket simulation with the new program simulations.

  3. Depending on results (how close agree with OpenRocket, reasonableness, state of length/mass/engine tracking project or other critical comp work) do analysis changing one variable at a time alongside OpenRocket to determine how key variables affect flight dynamics and how well the different software agrees.

Non Sequential tasks:

  • Do research into the accuracy difference between chosen program/s and OpenRocket

  • Throughout this process keep good documentation to ensure if the team ever revisits this we have good information as well as creating a way to onboard new flight sim people well.

Required Documentation

  • Page on confluence describing advantages and disadvantages of each simulation program. (make notes about user experience of using each piece of software)

  • Design doc to stay coordinated and know what work is being done

Deliverables Timeline

  1. Onboard new members, meeting going over what works needs to be done and planning the work that will be done soon. (done by Oct 1) 

  1. Research RASAero, Rocksim and RocketPy to determine the overall advantages and disadvantages of each. Use data and solid reasoning to decide on one or two to pursue further. Have info ready for a meeting to decide by Oct 15

    1. As part of above make a simple rocket in the software chosen (or in other if desired) to learn how to use the software. (start before Oct 15 and have decent grasp of main concepts using software by Oct 22)

  2. Make a rough model of our rocket in the one or two programs of choice (potentially using a COTS motor if this simplifies the process) (Done by Nov 5)

    1. If it is feasible, model our engine in the program/s of choice to be able to directly compare the OpenRocket simulation with the new program simulations.

  3. Depending on results (how close agree with OpenRocket, reasonableness, state of length/mass/engine tracking project or other critical comp work) do analysis changing one variable at a time alongside OpenRocket to determine how key variables affect flight dynamics and how well the different software agrees. (November/December)

  4. After this, determine next steps. Most likely planning for comp stuff.

Non Sequential tasks:

  • Do research into the accuracy difference between chosen program/s and OpenRocket and why this is the case.

  • Throughout this process keep good documentation to ensure if the team ever revisits this we have good information as well as creating a way to onboard new flight sim people well.

Cost Analysis

No costs 

Integration Concerns and Stakeholders:

Mainly flight dynamics. Mostly a research project though at this point so no huge risks

Design Log: