Fix for compatibility with OpenMDAO:3.39

[Kenneth-T-Moore]

Summary

1. Modified some of the viewers to adapt to the loss of hybrid promoted names in OpenMDAO 3.39.
2. Added a benchmark that runs the cycle examples so that we can be warned when something goes wrong with them.

Related Issues

• Resolves Compatibility with OpenMDAO 3.39.0 #100

Backwards incompatibilities

None

New Dependencies

None

[Kenneth-T-Moore]

@drhode-icct @arushkumarsingh
Can you let me know if this fixes the problem for your models?

[drhode-icct]

Yes @Kenneth-T-Moore @arushkumarsingh , this fixes the errors I had with the viewer file, also required some modifications to my own model to work properly (since I was referring to add_cycle_param variables as PNT_name.variable_name. Now that this is not possible, maybe mentioning this in the release notes could be helpful for other users.) Thanks for the fix!

[arushkumarsingh]

Yeah, it works,

Will need a change in this function, as sometimes units are also passed to get a value.
def get_val(prob, point, element, var_name)

Changes to:

def get_val(prob, point, element, var_name, units=None)
val = prob.get_val(f"{point}.{element}.{var_name}", units = units)
val = prob.get_val(f"{element}.{var_name}", units=units)

[Kenneth-T-Moore]

Hey, @arushkumarsingh
I've got a units argument added to the get_val call, so that you can convert between compatible openmdao units.