OpenMDAO / OpenMDAO/Aviary

Add vehicle efficiency metrics

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

Nobody has claimed this yet.

request
Dominant language
Python
Stars
287
Forks
140
Avg merge
6d 14h
Merged PRs (30d)
18

Description

Desired capability or behavior.

Calculate energy consumption per available seat-mile and per per tonne-kilometer as an output of the Performance subsystem

Suggested implementation.

In performance post-mission, add a component that calculates the metrics:
energy/seat-mile (MJ/pax * mi) = total mission energy consumption / (number of passengers * mission range)
energy/tonne-km (MJ/t * km) = total mission energy consumption / (useful load * mission range)

I am suggesting useful load be used rather than passenger + cargo mass as useful load is more generic and broadly applicable to future aircraft concepts that might have unusual configurations, but a simple sum of pax + cargo might be more intuitive for users. Units are given in openmdao format (t is metric ton)

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 locating the Performance subsystem's post-mission entry point and the existing outputs for total mission energy, passengers, useful load, and mission range. Add the two requested efficiency metrics using the stated units and formulas, resolve the useful-load interpretation, and verify the outputs with the subsystem's existing tests.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.