After running demoDesignVars, the pyGeo design variables appear to be left in whatever state they were in the last written frame. This is an issue because if you then run ADflow, you will be not be the running the baseline geometry you think you are.
Steps to reproduce issue
Setup an ADflow/pyaerostructure case with a DVGeo object
Run demoDesignVars
Run ADflow/pyaerostructure and look at the result in tecplot (the result shown below is from the private MACH tutorial)
Current behavior
Geometric DV's remain in their last perturbed state.
Expected behavior
Geometric DV's should be reset to their original values at the end of demoDesignVars
I don't understand how this is happening as the DV's appear to be correctly reset in all the intermediate frames, it's only the final perturbed state that is not.
Description
After running
demoDesignVars, the pyGeo design variables appear to be left in whatever state they were in the last written frame. This is an issue because if you then run ADflow, you will be not be the running the baseline geometry you think you are.Steps to reproduce issue
demoDesignVarsCurrent behavior
Geometric DV's remain in their last perturbed state.
Expected behavior
Geometric DV's should be reset to their original values at the end of
demoDesignVarsI don't understand how this is happening as the DV's appear to be correctly reset in all the intermediate frames, it's only the final perturbed state that is not.