-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Started Notebook Fails #114
Comments
Tks for sharing this! Version Release will be adressed as soon as possible, I'll handle it myself. |
Hey, sorry for the failure on the asap part. @giovaniceotto can you help me to understand if we need to merge anything from "develop" do "master" before realeasing the new version? If positive, let's select the pull request and create the merge. |
@Gui-FernandesBR, I do believe we may have a couple of things in the develop branch that could be merged into master before the new version. Could we discuss it further over discord, together with the automatic release? |
Great idea Gio! I will propose an appointment on your agenda for tomorrow and then we meet on discord |
Last release was created on 16th August. Since that day, the following PR were merged on develop branch:
@MrGribel could you please check and validate the proposal giving your OK (or NOK) for each line? |
Master branch should contain stable code. I doubt we have many users extensively testing our dev branch since it is not the default one, meaning we ourselves need to check if it is ready to deploy. Everything seems to be running well on my end and imo these PRs are too unrelated to have broken anything hidden due to conflict. Just a thing: develop currently has a CI build error that should probably be adressed first. After that, feel free to merge and create a new release. EDIT: Just noticed that since this is our first time merging from dev: it is 74 commits behind master... |
Works fine now, tks to all team! |
Describe the bug
When running the getting started notebook (which can be done via Colab), it fails and throws and error in the Dynamic Stability Analysis section.
The error happens because a typo was fixed in every file of the master branch, including in the notebook (#106). The typo in question was the incorrect spelling "Costum" instead of "Custom", which affects the "CustomAtmosphere" argument that can be used in the
Environment.setAtmosphericModel
method. However, the current version of rocketpy released on PYPI (0.9.8) does not yet incorporate this typo fix.To Reproduce
ValueError: Unknown model type
after running the Dynamic Stability Analysis cellExpected behavior
The entire notebook should run without errors.
Screenshots
Solution Sugestion
Release a new version!
The text was updated successfully, but these errors were encountered: