User Interface for Modeling Aircraft

[Dawson-Manning]

Summary

This commit adds a interface for users to easily create and edit models to use for optimization. Interface includes names, units, and descriptions of each variable and sorts them into four tabs for Aircraft, Dynamic, Mission, Setting and sorts each variable name into containers based on the subheading "wing", "engine", etc. Additionally, there is an added search feature which allows for users to quicky search a variable name to be edited. Once finished with entering inputs, the user's inputs and remaining entries, which autofill to default values, are written to a csv file in a format that can be used by Aviary. Image of interface attached below.

All information is pulled from Aviary>aviary>variable_info>variable_meta_data.py and Aviary>aviary>variable_info>variables.py thus it automatically updates and adds variables to the interface when variables are added to Aviary's meta data.

Additional edits were made to Aviary>aviary>variable_info>variables.py to keep formatting consistent with other variables.

Related Issues

• Resolves #

Backwards incompatibilities

None

New Dependencies

None

[Dawson-Manning]

With new commits, the gui can now be ran using aviary command . Additionally, all Dynamic.Mission.**vars were removed along with the associated tab. The gui will now indicate to the user via command prompt when a file has been saved with "Summit", "File->Save", and "File->Save as...", The gui will now indicate to the user via command prompt when a file has been opened with "File->Open" and "File->Open & Display".

[crecine]

There are some variables that have different defaults for GASP vs FLOPS (see utils/legacy_code_data). It might be a good idea to allow the user to load the defaults from one of those before they start making changes.

[Dawson-Manning]

There are some variables that have different defaults for GASP vs FLOPS (see utils/legacy_code_data). It might be a good idea to allow the user to load the defaults from one of those before they start making changes. @crecine I am able to do this, however since there are far more default values for flops the resulting csv file would be a mixture of FLOPs and GASP default values as this interface prints all lines from the variable meta data except dynamic variables. Is this an issue???

[crecine]

@crecine I am able to do this, however since there are far more default values for flops the resulting csv file would be a mixture of FLOPs and GASP default values as this interface prints all lines from the variable meta data except dynamic variables. Is this an issue???

I meant adding a button (or something else) to allow the user to load one of the legacy defaults after it reads the variable_meta_data

[hschilling]

Thanks, Dawson!

In the search tab, if I put something in the search box, do a search, and then press Clear, the results go away as they should but the search box still has what I typed into it. Should it? I think most search interfaces clear the search text box also.

[hschilling]

When you do a Submit, the text in the terminal has a typo

Model successfully Seved to Aircraft_Model.csv

[hschilling]

This field looks like it might be hard to fill out. Can a popup menu be used for values that have a limited number of options?

[hschilling]

Not sure what is different from when I tried the Search and commented about it, but now when I do searches, nothing shows up. For example, searching for "wing" results in no results.