Some users have had issues installing OpenMDAO under certain circumstances. In this section, we’ll address some of the most common installation pitfalls. We’ll also discuss what you can do to receive assistance when faced with an installation problem or error message that you don’t understand.
The OpenMDAO Open Source Question and Answer (OSQA) Forum (http://openmdao.org/forum) is the first place that you should go to find an answer to your question. Search this forum before asking a question or commenting on existing questions (e.g., “I have this problem, too!”). If a question is asked just once, it’s probably unique. Remember to follow forum etiquette – upvote and downvote answers and comments, and formally accept an answer when you are satisfied.
envdump
You may have trouble installing OpenMDAO or experience a test failure, and the reasons why might not be readily apparent. If this happens, it may help to examine the environment where you are attempting the installation. OpenMDAO provides a specific environment-dumping script for extracting this information.
If the installation was successful, then from a prompt in an activated environment, you can simply type:
envdump
A full output of the machine’s environment will be printed to the screen.
If the installation was not successful, then you won’t have the script yet, but you can download the envirodump.py script from the Miscellaneous Downloads section at openmdao.org/downloads. Once the script is downloaded, to manually run it, type:
python envirodump.py
This should produce the same results as running the envdump console script. Sometimes, examining the output of the environment will expose obvious path problems that can expedite the troubleshooting process.
Capturing Envdump, Installation Output, or Test Output
At times, a problem will not have an obvious fix, and you might want to get help from the OpenMDAO developers. The first step, as discussed above, should be to post your question in the OpenMDAO forum. Posting in the forum makes sure that the answers are archived for others who have the same problem. If the problem can’t be solved easily though, the OpenMDAO developers might request more detailed information from you. In these cases you will need to capture the output of an attempted installation, a test run, or an envdump (or more than one of these events) and send the full report(s) to the OpenMDAO development team for inspection.
When directing standard output (I/O stream 1) and standard error (I/O stream 2) into the same file, try:
command 1> filename 2>&1
(Where command is something like python envirodump.py or openmdao test, and where filename is something like my_envdump.txt or my_testoutput.out.)
Once the outputs have been captured into properly named files, please email the files to the OpenMDAO development team using the email support@openmdao.org.
Windows Specific
Mac OS X Specific
Linux Specific