RocketPy

RocketPy copied to clipboard

Pull request type

• [x] ReadMe, Docs and GitHub updates

Checklist

• [ ] Tests for the changes have been added (if needed)
• [x] Docs have been reviewed and added / updated
• [x] Lint (black rocketpy/ tests/) has passed locally
• [x] All tests (pytest tests -m slow --runslow) have passed locally
• [x] CHANGELOG.md has been updated (if relevant)

New behavior

A new flight has been added to our "Flight Examples" page!

Breaking change

• [x] No

Additional information

Many thanks to Giorgio Chassikos and the Western Engineering Rocketry Team

The rocket is from Spaceport 2022, but the environment on the notebook is using 2023 data. Is this correct?

Also, something is wrong here:

I was running late and wanted publish it as fast as possible, so I used the environment of 2023, which was already saved in our repo, rather than download the 2022 data from Copernicus.

Do you think it's so important to update with the 2022 environment data?

Regarding the acceleration, this is interesting, right? Seems like the telemetry data is presenting the acceleration as the derivative of speed. After burnout, the rocket constantly reduces its speed, and the telemetry plot represents it.

RocketPy's acceleration will always be in absolute value, no matter if the rocket is speeding up or down. Probably because the acceleration is calculated as the sqrt of ax2 + ay2 + az**2

If you want the plots to match perfectly, we could apply the abs() function to the telemetry data. Is this important?

I see this as a beautiful thing.

Just in case you hadn't seen it yet, the dataset I sent @Gui-FernandesBR from our other flight computer (the TeleMetrum) had a full set of speed data (unlike the TeleMega data). It could be used for a speed comparison to RocketPy. The data from that flight computer is also a lot smoother than the data from the TeleMega.

I swapped the telemetry files and applied a normalization in the data. This is the final plot:

@MateusStano ready for review please