Added explicit om namespace import to docs.

[robfalck]

Summary

The getting_started and basic_user_guide docs will now explicitly show the import of the om namespace, which was previously hidden as part of the logic to install it on colab if necessary.

This also changes the header which installs OpenMDAO on colab so that it doesn't import the OM namespace. Doc examples will fail if om isn't imported in a subsequent code block.

Related Issues

• Resolves Explicitly show importing of om namespace in docs. #2163

Backwards incompatibilities

None

New Dependencies

None

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[Kenneth-T-Moore]

@robfalck : You'll need to go to openmdao/docs/openmdao_book/tests/test_jupyter_output_linting.py:LintJupyterOutputsTestCase.test_header and change the test so that it checks notebooks for the new header text.

[Kenneth-T-Moore]

Looks like you missed some om imports in the distributed tests. They use a separate python env from the single-proc cells. You can find these locally by running the tests that live below openmdao/docs .

[coveralls]

Coverage decreased (-0.4%) to 88.905% when pulling 9c178dd on robfalck:import_om2 into 77353f8 on OpenMDAO:master.