Skip to content

Standardize Geometry Report #1317

Open
Open

Description

@cmbenne3

Desired capability or behavior.

Ideally we would have a single 'Aviary geometry' report that could display useful data to the user regarding the geometry that has been input, and the geometry that has been calculated and run in the problem. This is particularly important when a user has completed a custom optimization where some aspect of the geometry is included as design variables.

FLOPS and GASP have different input and output variables for geometry, so creating a single unified report is tricky.
PR #1314 upgraded the report to add more variables, some are only available for GASP or FLOPS problems and so the report always has 'unavailable' data regardless of problem type.

This issue requires discussion on best approach, variable search to check if there are anymore useful variables that should be reported and implementation of improved geometry report.

This issue replaces the ToDos in the code:

Image

Suggested implementation.

Team needs to discuss and decide on approach:

  1. Leave as is - report always has same format and same number of variables, user just needs to look past the 'unavailable' data.
  2. Generate dynamic variable lists depending on the geometry subsystem type (FLOPS, GASP, External)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    requestSuggestion for new feature or change

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions