Create component to unify passenger mass calculations

Open
  • Is something wrong?
#1,345 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

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

request
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.

Image
Suggested implementation.

No response

Dominant language
Python
Stars
294
Forks
144
Avg merge
6d 15h
Merged PRs (30d)
6

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenMDAO/Aviary

All issues in OpenMDAO/Aviary

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.