ENH: create a dataset of pre-registered motors.

[leogrosa]

Pull request type

• Code changes (bugfix, features)
• Code maintenance (refactoring, formatting, tests)
• ReadMe, Docs and GitHub updates
• Other (please describe):

Checklist

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

Current behavior

The user had to add its own .eng file to use the method GenericMotor.load_from_eng_file() to create a GenericMotor from it, and RocketPy didn't have a dataset of pre-registered motors.

New behavior

RocketPy now has its own dataset of pre-registered motors, containing 63 .eng files, located in rocketpy/datasets/motors/.
Three functions are now present in utilities.py to help:

• list_motors_dataset(): returns a list of all available motors names;
• load_motor_from_dataset(): load a GenericMotor from a motor name from the dataset;
• show_motors_dataset(): prints the list of available motors, useful for quick inspection in terminals and Jupyter notebooks.

Breaking change

• Yes
• No

Additional information

The user guide has documentation for the three new functions:

• The following test didn't pass locally:

FAILED tests/integration/test_environment.py::test_rap_atmosphere - ValueError: The chosen launch time '2025-05-05-02: UTC' is not available in the provided file. Please choose a time within the range of the file, which starts at '2025-05-06-01 UTC'.

To be discussed

• Should this dataset be installed with the default installation of RocketPy using pip? For now, the size of the dataset isn't big, so the easiest path is to just add it in the repo. However, in the future, it may become big enough to make it optional. Preparing the repo right now could be a good idea -- but it would demand changes in the PyPI pipeline.

[Gui-FernandesBR]

Should this dataset be installed with the default installation of RocketPy using pip? For now, the size of the dataset isn't big, so the easiest path is to just add it in the repo. However, in the future, it may become big enough to make it optional. Preparing the repo right now could be a good idea -- but it would demand changes in the PyPI pipeline.

Well, I believe it would be nice if the installation was optional. I think it is worth to search how to do that.
It would be nice to ensure a lighter installation by default.

One my side, there are two main concerns:
1 - You had to duplicate the .eng files in the repo. Isn't there any way wehre you don't need the new rocketpy/dataset folder, and instead simply download the data/ folder?
2 - Is there any particular reason for creating the new functions as utilities instead of methods of the GenericMotor class? (I'm not saying one option is better than other, I'm just trying to understand)

[leogrosa]

@Gui-FernandesBR, ok, I'll search for a nice way to make it optional and discuss it in the weekly. I know that it will involve another member of the team that has access to the PyPI configuration.

Regarding your concerns:

1 - There are ways, but the team and I discussed in the weekly that creating the datasets directory would be a good choice because:

• It separates what is meant to be used programmatically, as a resource (the datasets/ directory), from what is meant to be used in examples or sandbox exploration (the data/ directory), organizing it in a structured way (in this case, only having .eng files for motors, and nothing else);
• It allows RocketPy to reference the dataset in other parts of the code using rocketpy.datasets. I believe it wouldn't be good to reference the data folder like that, since it's not inside the rocketpy directory;
• It is inspired in other well-stablished projects, like the color palettes in seaborn, or the datasets from scikit-learn (sklearn.datasets).

2 - I thought it would fit better in the utilities because there may be future functions that also use the datasets directory, but are not necessarily related to the GenericMotor class. However, the fact that I've created the documentation inside the GenericMotor part in the user guide looks a little bit like an inconsistency haha, even though I thought it would be better for it to be there when thinking about its use case.