Skip to content

Post revamp payload range#812

Merged
jkirk5 merged 59 commits intoOpenMDAO:mainfrom
aalemu1:post-revamp-payload-range
Aug 7, 2025
Merged

Post revamp payload range#812
jkirk5 merged 59 commits intoOpenMDAO:mainfrom
aalemu1:post-revamp-payload-range

Conversation

@aalemu1
Copy link
Copy Markdown
Contributor

@aalemu1 aalemu1 commented Jul 7, 2025

Summary

Summary of PR.

Adds payload range functionality through a toggle within csv file, settings:payload_range,true. As well as rewrites the run_off_design_example.py for convergence.

Related Issues

Backwards incompatibilities

None

New Dependencies

None

Comment thread aviary/subsystems/mass/flops_based/landing_gear.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
Comment thread aviary/interface/methods_for_level2.py Outdated
@aalemu1 aalemu1 requested a review from jkirk5 July 21, 2025 15:37
@aalemu1 aalemu1 requested a review from cmbenne3 July 24, 2025 16:28
range_2 = float(self.get_val(Mission.Summary.RANGE)[0])

# check if fuel capacity does not exceed sizing mission design gross mass
gross_mass = float(self.get_val(Mission.Summary.GROSS_MASS)[0])
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
gross_mass = float(self.get_val(Mission.Summary.GROSS_MASS)[0])
gross_mass = float(self.get_val(Mission.Design.GROSS_MASS)[0])

If you run payload-range after running a different off-design mission you might pull the wrong mass here if you don't specifically call for design? Just covering an edge case

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The function checks that the mission the payload/range is being ran on is a sizing mission and would disallow the user from attempting it. Therefore this edge case, I don't believe is possible anymore.

@jkirk5 jkirk5 enabled auto-merge July 31, 2025 17:49
@jkirk5 jkirk5 added this pull request to the merge queue Jul 31, 2025
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jul 31, 2025
@jkirk5 jkirk5 added this pull request to the merge queue Aug 6, 2025
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Aug 6, 2025
@jkirk5 jkirk5 added this pull request to the merge queue Aug 7, 2025
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Aug 7, 2025
@jkirk5 jkirk5 added this pull request to the merge queue Aug 7, 2025
Merged via the queue into OpenMDAO:main with commit 7a94c8b Aug 7, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Design mass changes for off design FLOPS missions

4 participants