OpenMDAO / OpenMDAO/Aviary

FLOPS-based additional engine mass does not support multi-engine

Open
#1,095 0 comments 0 reactions 0 assignees View on GitHub

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.

Copied from source code: "temporarily using engine-level additional mass and multiplying by num_engines to get propulsion-level additional mass"

See EngineMiscMass of subsystems/mass/flops_based/misc_engine.py.

Is your feature request related to a problem? Please describe.

No response

Associated Bug Report

No response

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reading EngineMiscMass in subsystems/mass/flops_based/misc_engine.py and trace how engine-level additional mass is converted to propulsion-level mass. Update the behavior so multi-engine configurations are supported correctly, then verify that the resulting propulsion-level additional mass matches the configured engine count.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.