Marco Mangano

Nice stuff! I have tested it really quickly and I am experiencing some issues already: - (minor thing, but it would be good to have a quick way for the...

It does look that the two issues are essentially the same, and I think what @nwu63 recommended (showing all the shared values, and add the major-only where applies) still makes...

Bumping this up (even if I am not wiling to work on it any time soon) because I really don't like the low reliability of the output messages here

Hello, this feature has not been implemented so far. To monitor and plot the optimization history, you can use [OptView](https://mdolab-pyoptsparse.readthedocs-hosted.com/en/latest/postprocessing.html#optview). You can also access the history file as done in...

@anilyil this issue can be closed, right?

The links I tried are working, is this good for review?

@eirikurj I did not look at the log, but I tested a few crosslinks top other RTD pages (e.g. pyoptsparse) and they worked. I think I am misunderstanding the goal...

Thanks for the PR @lukasmu, and sorry for my late reply! I agree this is a very nice feature to have. My comments so far: - Is the backwards compatibility...

I agree with your points, but I am not sure if this is worth a major bump. Unless we actually rewrite a substantial part of the code or rearrange a...

If I understood @anilyil offline comment correctly, one implementation reason to explain this ordering is that in `DVGeo.update` the links between the FFD control points and the reference axis nodes...