Eytan Adler

Aspect ratio is not computed for the meshes. However, you can certainly compute it with existing quantities in the model by making an OpenMDAO component and use the result as...

> `DVConstraints` -> `GeoConstraints` `DVGeo` -> `GeoParam`, `GeoParam_FFD`, `GeoParam_FFDMulti`, `GeoParam_VSP`, ... etc I like this suggestion, though without the underscores in the new `DVGeo` names

Yes it's ready. The checks are hanging because they changed name (1.6.0 -> 1.7.0), so the required ones I have setup are no longer valid. If you're good with these...

Currently, the actuator zone's thrust cannot be set through the `AeroProblem` as expected if the actuator zone uses the `simpleProp` type. The `simpleProp` uses the `thrust` attribute from `actuatorRegionData` rather...

I don't have anything unit testable but the basic behavior necessary is that this wasn't working before: ```python solver = ADFLOW(options=options) solver.addActuatorRegion( "az_surf.x", actType="simpleProp", axis1=np.array([0.0, 0.0, 0.0]), axis2=np.array([1.0, 0.0, 0.0]),...

@shamsheersc19 I deleted it because I realized I overlooked the force per length to force per volume conversion and it made sense after. Thanks for the clarification!

Yes, I’ll add it here. I just haven’t got around to it yet.

I did a first pass of forward mode derivatives for the MPhys DVGeo component. I'm not super familiar with the parallelization hacks, so @anilyil please check those and let me...

> What's the status of this PR @eytanadler? I made my own implementation of fwd mode (PR #254), but looking at this PR in further detail you appear to have...

This is finally ready for review