In the old docs, we could pull, for example, a component or group definition model from the openmdao example suite and display it for the reader. There are some cases where we do this, but don't build and run a model in the feature doc. This was fine because most of those examples were used in many places. With notebooks, now it is just python code, so it won't be updated for changes in API. To remedy this, we need to add some tests in code cells with hidden-input and hidden-output.
For example, SubProbComp in openmdao_book/features/core_features/working_with_derivatives/total_compute_jacvec_product.ipynb
Kenneth-T-Moore
commented
3 years ago
In the old docs, we could pull, for example, a component or group definition model from the openmdao example suite and display it for the reader. There are some cases where we do this, but don't build and run a model in the feature doc. This was fine because most of those examples were used in many places. With notebooks, now it is just python code, so it won't be updated for changes in API. To remedy this, we need to add some tests in code cells with hidden-input and hidden-output.
For example,
SubProbCompinopenmdao_book/features/core_features/working_with_derivatives/total_compute_jacvec_product.ipynb