-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Windows installation guide produces failed compilation Error: invalid register for .seh_savexmm\r. ' #4749
Comments
@twiecki I got a working Windows conda env for pymc3. First by installing MinGW and following these installation instructions, setting minwg bin folder to my Path environment variable. Then I did the following:
Cygwin was producing errors in the compilation step. |
Is that different from the windows installation instructions? Should we update them? CC @michaelosthege |
The Windows job in the CI pipelines for v3 also started failing recently. It's blocking PRs such as #4745 and #4741. For v4 the Windows job is still disabled, by the way 😬 |
@twiecki Yes the steps I posted are different from the windows installation instruction. The current windows installation instruction also does not mention the requirement of MinGW. @michaelosthege The compilation error stems from |
I just confirmed that after installing with However
FWIW I don't trust conda-forge when it comes to PyMC3. |
I do have Visual Studio installed, so maybe that gives me a headstart when it comes to compilation stuff. |
@michaelosthege maybe mingw is the safer option? |
When I do
I do not get any compilation error, so that works too. However I always get the |
I also have Visual Studio installed, but not with any specific C++ components since I do not work with C++ |
Our install instructions include We should specify OS-dependent dependencies in our requirements/setup.py/conda recipes. |
Okay, getting the BLAS stuff installed properly is really hard.. The On the plus side, by following the Getting |
With the sunode installation I do not get the BLAS warning so that seems to be working, but still get the To get a working truly working environment I turned to the official docker image,
but that also produces errors ...... |
The But try the following. This just worked for me and this time I confirmed with the getting started notebook too. (Not sure if I did that for my last comment last night.) environment.ymlname: pm3env
channels:
- conda-forge
- defaults
dependencies:
- ipywidgets=7.6.3=pyhd3eb1b0_1
- jupyter=1.0.0=py37_7
- libpython=2.1=py37_0
- matplotlib=3.3.2=haa95532_0
- mkl-service=2.3.0=py37h196d8e1_0
- numba=0.53.1=py37h4e635f9_0
- numpy=1.19.2=py37hadc3359_0
- pandas=1.2.1=py37hf11a4ad_0
- pip=20.3.3=py37haa95532_0
- python=3.7.9=h60c2a47_0
- python-graphviz==0.16=pyh243d235_2
- scipy=1.5.2=py37h9439919_0
- sympy=1.7.1=py37h03978a9_1
- pip:
- arviz==0.11.1
- fastprogress==1.0.0
- h5py==3.1.0
- openpyxl==3.0.7
- pymc3==3.11.2
- typing==3.7.4.3
- watermark==2.2.0
- xarray==0.16.2 conda create -f environment.yml
conda activate pm3env
conda install m2w64-toolchain |
When I do
I get the same error
I get a working env, with BLAS enabled and no compilation error. |
Not sure if that's good or bad. I added a warning to the wiki page and also linked to the comments above. |
I just updated the installation guide with a minimal version. |
Getting this error on Windows 10 after following the guide exactly. Have tried many suggestions to fix this problem and even completely uninstalled Anaconda and re-installed to start from scratch. Any help appreciated! Let me know if any more information would be useful in resolving this problem.
|
@edt-andrew I just tried with the I'm on Windows 10 with miniconda. Do you maybe have Cygwin or something like that installed? A quick Google search returned some results mentioning it. I don't have Cygwin on my system. Maybe that's the difference? |
I installed MinGW after seeing it suggested as a solution but didn't have that initially installed (error is the same). I don't have Visual Studio installed if that's relevant at all? Is there a parameter I can pass to pymc3 to force it to not use the compiler, even if just to check the problem is confined to compiling issues alone? |
You can set the Theano compile mode to |
Imports looked like this:
Same error as before... I appreciated the quick responses! Am I to understand these issues seem to be mostly confined to windows? |
This problem in particular may be Windows specific, but more in the sense that there is something wrong with the compilation dependencies that arises from an unlucky combination of packages.. The dependency tree looks different by platform.. |
Can you post a link to where I can get v4? https://github.com/pymc-devs/pymc4 this url says that project has ceased? |
We're referring to |
Hi again - that seems to have solved my compilation issues. However I seem to have a problem with DensityDist where I'm getting the below error. I note that the code example in the source code also breaks with this error (if fails on normal_dist.logp needing replaced with pm.Normal.logp first but subsequently fails with the same error). Am I correct in assuming this part of the codebase is just unfinished for the new version? Would commenting out the references to cls.rv_op.ndim_supp suffice as a quick fix? If this isn't the right place to be asking this question please to point me in the right direction! Thanks again for all your time.
|
Is this on |
I am not familiar with |
Thanks guys this is all very helpful to know. Is there a vague estimate on when those distributions will be refactored, or when the v4 release is planned? |
Hi, so did you solve the problem by installing the pymc4 instead of pymc3? I also met the same problem as you, and I followed up the installation guide from here, but the problem still existed. |
I followed up the same process, but I still got some errors, could you please help me solve this problem? #4922 |
I have the similar problem, I think maybe I have solved it.
in line 2191. Maybe you can try my way. |
@gourdchen I tried to follow you what suggested. For the @mick-phemex same installation issues as you and @michaelosthege directed me to the discussion you are having with him. So I'm trying to see if my Pymc3 issues go away if Anaconda mingw compilers are set-up correctly in the User environment variables per recommendation by @michaelosthege at Pymc3 Discourse web site. If I find a solution, I will post it here. Sree |
@gourdchen @mick-phemex Following the User Path variables information that @michaelosthege had posted in his conversation with you @mick-phemex I was able to overcome two issues I was dealing with:
Both of these issues had the same underlying cause: Anaconda packages were accessing the incorrect |
Description of your problem
By following the Windows installation guide and the getting started notebook I get the following error when calling
map_estimate = pm.find_MAP(model=basic_model)
Please provide a minimal, self-contained, and reproducible example.
Please provide the full traceback.
Please provide any additional information below.
Are there any other requirements that are missing in the windows installation guide that are missing?
Versions and main components
The text was updated successfully, but these errors were encountered: