OpenMDAO / OpenMDAO/Aviary

Initial guessing for some setups should be better integrated

Open
#95 1 comment 0 reactions 3 assignees View on GitHub

@Kenneth-T-Moore is already working on this.

Since Feb 11, 2026.

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

Description

Desired capability or behavior.

After wrestling with GASP-based initial guessing, I'm putting it aside for a bit.
We should move the initial guessing that currently occurs in create_vehicle out to the correct method within methods_for_level2.py, set_initial_guesses. Unfortunately there are intermediary uses within the code for the initial guesses. I haven' been able to parse them apart or refactor them too easily.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.