OpenMDAO / OpenMDAO/Aviary

Need checks of number of engine locations

Open
#1,189 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.

Note in from Jason: There are also no checks that number of engine locations is consistent with half of number of wing mounted engines, which should get added to preprocessor

See issue # 1189 in DetailedWingBendingFact of subsystems/mass/flopsed_based/wing_detailed.py
See issue # 1189 in BWBDetailedWingBendingFact of subsystems/mass/flopsed_based/wing_detailed.py

Suggested implementation.

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 in subsystems/mass/flopsed_based/wing_detailed.py, reading DetailedWingBendingFact and BWBDetailedWingBendingFact alongside the preprocessor logic. Trace how engine locations and wing-mounted engine counts are represented, then add checks that their count is consistent with half the number of wing-mounted engines. Run the relevant existing test suite to verify the validation behavior.

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
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.