Should automatically do this in the Fun3dAim and TacsAim according to Marshall in that it will only generate a new mesh if the topology change is significant enough.
So then maybe we need to turn on mesh morphing flag even for remeshing case - and that would do it?
Need a way to classify the phases of the design history into:
1) moving towards xstar, significant changes in function values and design variables 2) oscillating around xstar due to remeshing noise
Solutions: could think of some mathematical rules, use machine learning.
Alternative but weaker resolutions: