Installation docs update

[kanekosh]

Purpose

This PR adds installation instructions using OpenMDAO's build_pyoptsparse script on the installation documentation page.
This script has already been mentioned on the IPOPT page, but I think it's worth putting this on the installation page for more attention. (This script is probably the easiest way to install IPOPT and SNOPT, especially on macOS, but I recently realized that some people are not aware of it.)

Expected time until merged

a week

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Checklist

• I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[codecov]

Codecov Report

Merging #350 (67a164f) into main (fe2a819) will decrease coverage by 11.92%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #350       +/-   ##
===========================================
- Coverage   84.42%   72.51%   -11.92%     
===========================================
  Files          22       22               
  Lines        3307     3307               
===========================================
- Hits         2792     2398      -394     
- Misses        515      909      +394     

see 7 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[ArshSaja]

Nice!, just a quick question, is IPOPT an open-source? if So, we can point out that.

[kanekosh]

Nice!, just a quick question, is IPOPT an open-source? if So, we can point out that.

Yes, IPOPT is open source and that is already mentioned in https://mdolab-pyoptsparse.readthedocs-hosted.com/en/latest/optimizers/IPOPT.html . So I think we don't have to say that on the installation page?

[ArshSaja]

Nice!, just a quick question, is IPOPT an open-source? if So, we can point out that.

Yes, IPOPT is open source and that is already mentioned in https://mdolab-pyoptsparse.readthedocs-hosted.com/en/latest/optimizers/IPOPT.html . So I think we don't have to say that on the installation page?

Yes, forgot it is mentioned there. For consistency, we can point out the IPOPT installation page similar to how you are pointing out the SNOPT installation page.

[kanekosh]

@ArshSaja added the link to the IPOPT page.

@marcomangano I think the line you added about the SNOPT precompiled library better fits under the conda section, so I moved it. Does this look good to you?

[ArshSaja]

@ArshSaja added the link to the IPOPT page.

@marcomangano I think the line you added about the SNOPT precompiled library better fits under the conda section, so I moved it. Does this look good to you?

Thanks, looks good!

[marcomangano]

@marcomangano I think the line you added about the SNOPT precompiled library better fits under the conda section, so I moved it. Does this look good to you?

Yeah fair, the details are in the SNOPT page anyway!

[marcomangano]

Tests are passing but somehow the info is not passed back from Azure. For now, can @eirikurj or @anilyil override the test requirements and merge this? Thx

[eirikurj]

Builds should be reported properly now. Unrelated, but we really should do something about codecov...