-
Notifications
You must be signed in to change notification settings - Fork 30
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
undefined symbol: mem_fence #15
Comments
I forgot to mention that I'm working with the most recent sources from the git repository. |
Hello, |
Hello Konstantin, I did not try opencel before because it was not required. But the powder sample necessarily needs opencl. Here is the output of info_opencl.py
By the way I'm using the software inside a virtual machine because I was not able to get xrtGlow working on my windows machine. So I could also try to use another linux distribution if there is a preferred one. Thanks for your assistance |
I've never worked with OpenCL in a virtual machine. I find it weird to seek for hardware acceleration in a virtualized solution. I don't even know if this should work. As to the issue, I see your pocl is old. I see in their GitHub that mem_fence was implemented quite recently. You may have reasons to prefer pocl over Intel's CPU-only Runtime Packages but I would try the latter first. As to the trouble with xrtGlow in Windows, please see one of the latest closed Issues. If in Anaconda, it's better to install pyopengl from the Gohlke's page. If in WinPython, you should install it by pip from it's standard pypi source. Don't know why this is so. |
It is possible to run opencl applications in virtualbox, but you still have to install proper opencl driver. Download and install the Intel OpenCL runtime from https://software.intel.com/en-us/articles/opencl-drivers |
Yes the reason is lack of knowledge and that this is the default dependency for pyopencl in debian ;-). And I was not aware that there are different implementations of opencl. I have now installed the intel opencl drivers on my windows host and pyopencl from conda-forge. This way the xrd example works but is rather slow. It takes approximately 90s for one step to calculate. Can this be expected on my ~5 year old cpu or is there still something misconfigured. Regarding xrtGlow on Windows I will try to use the Gohlke *.whl packages. Thanks so far for your assistance |
It's all about the double precision performance, the code calculates the reflectivities for each combination of HKL and takes the highest probable, so you could try to reduce the PowderSample.hkl for faster results (strictly speaking we should've used the Monte-Carlo discrimination here, but this would slow down the process dramatically. it's an easy fix after all, just let me know if you are interested in a bit more precise result for a price of overall performance). |
I have implemented OpenCl as suggested in this issue.
|
Is this in the XRD example or it's something else? |
Meanwhile I have downloaded the last release xrt 1.3.2 and now it works. |
Recently I found your software and wanted to give it a try to model some powder diffraction experiments. I already was able to model my instrument but now I have troubles with the powder sample.
Whe I run the xrd example file I get the following error in the gui:
I'm working on a Debian stretch system.
Do you have any hints how to solve this problem?
Thanks
Armin
The text was updated successfully, but these errors were encountered: