Move mass_per_flight_crew to Aviary variable
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
A note from Jason in subsystems/mass/flops_based/crew.py: mass_per_flight_crew should be its own variable.
If it is valid, it can be added quickly.
See issue # 1190 in _mass_per_flight_crew() of subsystems/mass/flops_based/crew.py.
Suggested implementation.
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read subsystems/mass/flops_based/crew.py at _mass_per_flight_crew() and compare nearby Aviary variable declarations. Confirm whether mass_per_flight_crew is valid as its own variable, then verify the relevant mass subsystem behavior with the repository’s existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100