mdolab / mdolab/pyoptsparse

SNOPT Installation Documentation

Open
#447 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
270
Forks
123
Avg merge
1d 18h
Merged PRs (30d)
3

Description

I am trying to install SNOPT for use in OpenMDAO. The documentation is a bit unclear of how to complete this installation given the precompiled libraries. So far I have:

  1. Set the environment variable SNOPT_LICENSE to the file path of the .lic
    set SNOPT_LICENSE "C:\Filepath\snopt7.lic"
  2. Download the modified setup.py file, added the location of my .dll and .lib files to the snopt7 path variable, and placed it in pyoptsparse\pyoptsparse\pySNOPT
  3. Set the environment variable PYOPTSPARSE_IMPORT_FROM to
    pyoptsparse\pyoptsparse\pySNOPT\source\f2py
  4. Run the command
    conda install -c conda-forge pyoptsparse

I have also tried following the installation script and documentation and documentation given by the OpenMDAO team, but could not get the -s option to work.

Are there more detailed instructions on how to complete this process? Perhaps more info on how to build the binding file would be helpful to ensure I'm completing this process correctly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing SNOPT installation documentation, the linked build_pyoptsparse installation script, and the modified setup.py used under pyoptsparse/pyoptsparse/pySNOPT. Trace how the precompiled .dll and .lib files, SNOPT_LICENSE, PYOPTSPARSE_IMPORT_FROM, and the binding under source/f2py are expected to work; done means the documentation gives reproducible installation and binding-build steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.