John Jasa

Make sure it's either for the full aircraft or individual engines consistently in every case

Currently, if you want to add span as a DV to your problem, you add `wing.geometry.span` whereas if you want to add twist you add `wing.twist_cp`. These are not consistent...

When aerostructural cases are ran, we see numbers being output. Add what these mean to the docs.

Make plot_wing callable from the file directly and document this

3

Make it easier for users to call plot_wing from the file directly instead of from the command line

Review documentation in depth and modify as needed

2

The docs were kind of stitched together from a variety of ideas at different times. Go through these docs holistically and update / rearrange as necessary.

Currently, symmetric wings that do not touch the symmetry plane are improperly reflected. In the visualization script `plot_wing`, we assume when we mirror the wing that the mesh goes right...

Currently, tests are tested, but not necessarily all examples.

This will help users know how to access variables in the problem

A few types of geom DVs are not tested in an analysis or optimization. Make sure at least the derivs and API of adding these are tested.