Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc cleanup #311

Merged
merged 4 commits into from Jul 28, 2017
Merged

Doc cleanup #311

merged 4 commits into from Jul 28, 2017

Conversation

robfalck
Copy link
Contributor

Removed reference to from openmdao.core.blah import Blah in the tutorials. Fixed a typo in the implicit component test documentation.

…ials. Fixed a typo in the implicit component test documentation.
@@ -32,7 +32,7 @@ Preamble
::

from __future__ import division, print_function
from openmdao.core.explicitcomponent import ExplicitComponent
from openmdao.api import ExplicitComponent

At the top of any script you'll see these lines (or lines very similar to these) which import needed classes and functions. On the first import line the `print_function` is used so the code in the script will work in python 2.0 or 3.0. If you want to know whats going on with the division operator, check out this `detailed explanation <https://www.python.org/dev/peps/pep-0238/>`_. The second import line brings in OpenMDAO classes that are needed to build and run a model.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this isn't part of your PR, but we should change python 2.0 and python 3.0 to either python 2 and python 3 or python 2.x and python 3.x.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also I think Python should be capitalized ;)

@@ -32,7 +32,7 @@ Preamble
::

from __future__ import division, print_function
from openmdao.core.explicitcomponent import ExplicitComponent
from openmdao.api import ExplicitComponent

At the top of any script you'll see these lines (or lines very similar to these) which import needed classes and functions. On the first import line the `print_function` is used so the code in the script will work in python 2.0 or 3.0. If you want to know whats going on with the division operator, check out this `detailed explanation <https://www.python.org/dev/peps/pep-0238/>`_. The second import line brings in OpenMDAO classes that are needed to build and run a model.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also I think Python should be capitalized ;)

@robfalck
Copy link
Contributor Author

It's unrelated but I forgot to put BalanceComp in openmdao.api, so that's tagging along with this one.

@naylor-b naylor-b merged commit ee2da61 into OpenMDAO:master Jul 28, 2017
@robfalck robfalck deleted the doc_cleanup branch March 5, 2020 15:36
hschilling pushed a commit to hschilling/OpenMDAO that referenced this pull request Feb 24, 2021
* changed fb and hs problems to use IPOPT

* Modified yaml file to build pyoptsparse with ipopt

* Fixed finite burn problem to solve with IPOPT accurately

* fixed error in yaml file

* added local pyoptsparse install script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants