Create component to unify passenger mass calculations
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the GASP and FLOPS mass components and the preprocessors that currently calculate passenger mass with bags; the issue does not name their files or tests. Trace how passenger variables feed aircraft design in both methods, then define and validate a shared component that produces the same passenger mass behavior for each.
Written by the indexing model from the issue text.
Description
Desired capability or behavior.
We should maybe add a component to calculate passenger_mass_with_bags so that we don't do it in preprocessors. This component should be added to GASP and FLOPS based mass so that users can use the same set of passenger variables to control aircraft design regardless of legacy code methods in Aviary.
Suggested implementation.
No response
- Dominant language
- Python
- Stars
- 294
- Forks
- 144
- Avg merge
- 11d 18h
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from OpenMDAO/Aviary
-
Consolidate Aircraft.Nacelle.WETTED_AREA & Aircraft.Nacelle.SURFACE_AREAPossibly taken @xjjiang claimed this 1 day ago. Openrequest
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenMDAO/Aviary#1346 · 1 comment · 1 assignee ·
Maintainers usually reply within 3 days
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 3 days
-
Move mass_per_flight_crew to Aviary variablePossibly taken @xjjiang claimed this 23 days ago. Openrequest
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenMDAO/Aviary#1190 · 1 assignee ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Simplify how mission range is specifiedPossibly taken @ehariton claimed this 3 days ago. Openrequest
OpenMDAO/Aviary#1347 · 1 comment · 4 assignees ·
Maintainers usually reply within 3 days
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#147104 ·
Maintainers usually reply within 1 day
-
premises-missing
Difficulty 1/5 Under an hour Newbie friendliness 88/100
WingedGuardian/GENesis-AGI#3801 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Document new required `shared-org-key` input for `obs-aw-dependency-review`Possibly taken @github-actions claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bot-triaged module: inductor oncall: pt2 topic: fuzzer triaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 4 days