MakeHuman no running OpenGL error - python

I've read all of the same error post on google, checked my python and opengl files then installed more python stuff (showing pertinent to this problem)
python-2.7.12_1
python3.4-3.4.5_1
python3.5-3.5.2_1
python-enum34-1.1.6_1
python3.4-PyQt5-5.6_1
python3.4-PyQt5-opengl-5.6_1
python-PyQt5-opengl-5.6_1
python-numpy-1.11.1_1
and from source
PyOpenGL-3.1.1a1
and I am still getting this error when trying to start mankhuman.py
NUMPY.VERSION: 1.11.1
Traceback (most recent call last):
File "./makehuman.py", line 827, in <module>
main()
File "./makehuman.py", line 817, in main
from mhmain import MHApplication
File "./core/mhmain.py", line 45, in <module>
import mh
File "./lib/mh.py", line 43, in <module>
from glmodule import grabScreen, hasRenderSkin, renderSkin, getPickedColor, hasRenderToRenderbuffer, renderToBuffer, renderAlphaMask
File "./lib/glmodule.py", line 42, in <module>
import OpenGL
ImportError: No module named OpenGL
I am now at a loss as I cannot figure it out.. anyone got an idea that may (will) work?

You need to install the packages that provide the OpenGL libraries. Usually these are included in the development or library packages for your graphics card. It doesn't seem like Void Linux installs dependencies for you, so you'll need to install them yourself, and this will depend on the graphics driver you're using. If you use mesa, install MesaLib-devel. If you use Nvidia, install nvidia-libs. If you use AMD, I don't know what you should install. I'm not familiar with Void Linux so you might need to experiment with variations of the above. Good luck!

Related

Error while attempting to import openai's universe

While importing openai's universe, i get these errors:
Traceback (most recent call last):
File "/Users/calvin/Desktop/universe-test/main.py", line 2, in <module>
import universe
File "/Users/calvin/universe/universe/__init__.py", line 22, in <module>
from universe import error, envs
File "/Users/calvin/universe/universe/envs/__init__.py", line 1, in <module>
import universe.envs.vnc_env
File "/Users/calvin/universe/universe/envs/vnc_env.py", line 11, in <module>
from universe.envs import diagnostics
File "/Users/calvin/universe/universe/envs/diagnostics.py", line 94
async = self.qr_pool.apply_async(self.method, (self._last_img, time.time(), available_at))
^
SyntaxError: invalid syntax
I've tried downloading a different version of gym, reinstalling universe, and nothing works. I have python 3.8.5 64-bit. My operating system is macOS Catalina 10.15.6. Any ideas?
async is now a special keyword, and as such, can't be used as a variable name.
That library appears to be made for Python pre-3.5. I believe your only options are:
Use a older version of Python 3 (async was intrduced in 3.5).
Edit the local copy of the library file to change the name to something else.
Check to see if there are any updates/forks to the library that fix that issue.

Fipy doesn't seem to want to use SciPy as a solver

According to the FiPy website, you need "at least one of the solvers", and they list SciPy as one possible "solver". I definitely have SciPy installed - I can import it with import scipy. I haven't formally installed FiPy with setup.py or anything like that, I just have the code in a folder called fipy. When I then go into the Python shell and type import fipy, I get:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "fipy/__init__.py", line 44, in <module>
from solvers import *
File "fipy/solvers/__init__.py", line 68, in <module>
raise ImportError, "Could not import any solver package. If you are using Trilinos, make sure you have all of the necessary Trilinos packages installed - Epetra, EpetraExt, AztecOO, Amesos, ML, and IFPACK."
ImportError: Could not import any solver package. If you are using Trilinos, make sure you have all of the necessary Trilinos packages installed - Epetra, EpetraExt, AztecOO, Amesos, ML, and IFPACK.
I've already tried doing this after formally installing FiPy via setup.py (using pip didn't work, I got some strange error relating to tensorflow). Setting the FIPY_SOLVERS environment variable didn't work either (same error).
I'm on Ubuntu with Python 2.7.
Based on File "fipy/__init__.py", line 44, in <module> and File "fipy/solvers/__init__.py", line 68, in <module>, you appear to be running FiPy 2.1.x, which is quite old.
Please upgrade.

Stuck on error loading scipy, using Homebrew install, on macOS Sierra

This happens when I try to do:
import scipy.io
Another scipy module, such as scipy.sparse, seems to be OK.
The root error is:
packages/scipy/special/__init__.py", line 636, in <module>
from ._ufuncs import *
ImportError: dlopen(/usr/local/lib/python2.7/site-packages/scipy/special/_ufuncs.so, 2): Symbol not found: ___addtf3
The full stack trace:
Traceback (most recent call last):
File "HistogramClassifier.py", line 3, in <module>
import scipy.io
File "/usr/local/lib/python2.7/site-packages/scipy/io/__init__.py", line 97, in <module>
from .matlab import loadmat, savemat, whosmat, byteordercodes
File "/usr/local/lib/python2.7/site-packages/scipy/io/matlab/__init__.py", line 13, in <module>
from .mio import loadmat, savemat, whosmat
File "/usr/local/lib/python2.7/site-packages/scipy/io/matlab/mio.py", line 12, in <module>
from .miobase import get_matfile_version, docfiller
File "/usr/local/lib/python2.7/site-packages/scipy/io/matlab/miobase.py", line 22, in <module>
from scipy.misc import doccer
File "/usr/local/lib/python2.7/site-packages/scipy/misc/__init__.py", line 51, in <module>
from scipy.special import comb, factorial, factorial2, factorialk
File "/usr/local/lib/python2.7/site-packages/scipy/special/__init__.py", line 636, in <module>
from ._ufuncs import *
ImportError: dlopen(/usr/local/lib/python2.7/site-packages/scipy/special/_ufuncs.so, 2): Symbol not found: ___addtf3
Referenced from: /usr/local/lib/python2.7/site-packages/scipy/special/../.dylibs/libquadmath.0.dylib
Expected in: /usr/lib/libSystem.B.dylib
in /usr/local/lib/python2.7/site-packages/scipy/special/../.dylibs/libquadmath.0.dylib
That's pretty much it. Google returns quite a few hits, but they're either very old, or not the same lib, or things that I've tried. The rest of this post is all the stuff I found/tried so far that didn't work.
Double checking python:
which python
/usr/local/bin/python
ls -l /usr/local/bin/python
lrwxr-xr-x ... /usr/local/bin/python -> ../Cellar/python/2.7.13/bin/python
I'm not currently using virtual env.
I think Homebrew is OK:
brew doctor
Your system is ready to brew.
This is after trying this:
brew update
brew upgrade
I've also tried uninstalling and reinstalling the scipy package, both with brew and with pip.
I've tried various other things, but don't want to mess up a working Homebrew setup.
Older posts that Google brought back talk about "cobra", as far as I know I'm not using that. "which cobra" doesn't return anything.
Other things from Google talk about the order of the library path, but that seemed to be if you were using the built-in python, which I don't don't think is applicable since I believe I'm using Homebrew's version.
Clearly it has something to do with a library, maybe fortran related, but what to type in to fix it... don't know where to start.
Try this: remove /usr/lib/libSystem.B.dylib temporarily and then reinstall scipy.

PYTHON DLL load failed

I usually code in Matlab but I found a nice piece of PYTHON code that I would like to use. However having downloaded the package it is proving difficult to run. I'm getting the following error:
Traceback (most recent call last):
File "C:\launch.py", line 29, in <module>
from src.smcsquare import SMCsquare
File "C:\src\smcsquare.py", line 32, in <module>
from scipy.stats import norm
File "C:\Python34\lib\site-packages\scipy\stats\__init__.py", line 338, in <module>
from .stats import *
File "C:\Python34\lib\site-packages\scipy\stats\stats.py", line 184, in <module>
import scipy.special as special
File "C:\Python34\lib\site-packages\scipy\special\__init__.py", line 586, in <module>
from ._ufuncs import *
ImportError: DLL load failed: The specified module could not be found.
The _ufuncs.pyd is there in the C:\Python34\lib\site-packages\scipy\special\ directory. I tried adding this to my PYTHONPATH but it made no difference. I have also tried so dll fixers but these have not helped.
Has anyone encountered this and did you find a solution?
As other have said, make sure your .whl file matches the version and 32/64bit of the python distribution you're using.
Next, the problem I was having was I forgot to download and install the extra "numpy+mkl" package per the instruction: http://www.lfd.uci.edu/~gohlke/pythonlibs/#scipy
So for me it was numpy-1.11.0+mkl-cp35-cp35m-win_amd64.whl, which I downloaded and then:
python -m pip install numpy-1.11.0+mkl-cp35-cp35m-win_amd64.whl
I had already installed the regular numpy package via pip, but I just installed this one over it and everything started working and has been fine so far.

Pystacia can't find MagickWand on OS X

For some odd reason Pystacia is not able to find MagickWand.h on OS X.
I tried to tweak $DYLD_LIBRARY_PATH and $C_INCLUDE_PATH but no luck.
I have imagemagick up and running.
$ mdfind MagickWand.h
/usr/local/Cellar/imagemagick/6.8.010/share/doc/ImageMagick/www/api/MagickWand/struct__MagickWand.html
/usr/local/Cellar/imagemagick/6.8.0-10/include/ImageMagick/wand/MagickWand.h
And keep getting this error:
>>> import pystacia
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Library/Python/2.7/site-packages/pystacia/__init__.py", line 193, in <module>
init()
File "/Library/Python/2.7/site-packages/pystacia/__init__.py", line 28, in init
raise TinyException('Could not find or load magickWand')
pystacia.util.TinyException: Could not find or load magickWand
I went further down to figure it out how pystacia looks for MagickWand.h:
from ctypes.util import find_library
resolved_path = find_library('MagickWand')
if not resolved_path:
raise PystaciaException('Could not find or load magickWand')
Still no lucky.
Looking to the latest pystacia code from bitbucket I realized that the version from pip is pretty old (from 2011) and a installation from the latest code solved my problem -- as I can afford to run unreleased code.
I also entered an Issue on bitbucket so the maintainer put out a new code release.

Categories

Resources