First off, if you have support questions, please go via the PyCUDA mailing
list. I've CC'ed them on this reply.
On Freitag 12 Juni 2009, you wrote:
> Hello Andreas, I'm Luiz from Brazil.
BOOST_COMPILER was introduced in the 0.93 release cycle--the instructions
you're following do not match the version you're using, which is 0.92. I'd
suggest you try version 0.93rc4, from here:
http://pypi.python.org/pypi/pycuda/0.93rc4
Andreas

Hi Guys-
I need to apply an affine warping to an image and use the result in
CUDA. What sounds like a better idea:
1) Write a CUDA kernel to do the filtering and interpolation, perhaps
using texture memory for the source image.
2) Try to figure out how to get the image into OpenGL and try to do
the image re-sampling there. I know OpenGL is meant for operations
like this, but I have no idea how hard it will be to get things
working from python.
3) Just do the warping on the CPU side using, say, OpenCV or
scipy.ndimage.affine_transform, and then transferring the data to the
GPU for the rest of my CUDA pipeline
The source image is 1024 x 768 single channel, getting resampled down
to 64 x 80 using a transformation matrix that gets computed online. I
have pretty minimal OpenGL experience, and none in a python context.
Cheers,
Drew

Hey everybody,
I know that when a call is made to a CUDA kernel, control immediately
returns to the calling function or program. But if I then immediately call a
memcpy from the changed gpu array to an array on the host, will the call
wait for the kernel to finish before executing the memcpy?
Thanks,
>>>Chris

Hi,
After pycuda installation I ran some examples provided. Every time I
run them, I get the following message:
/usr/lib/python2.4/site-packages/pytools-9-py2.4.egg/pytools/
diskdict.py:119: UserWarning: DiskDict will memory-only: a usable
version of sqlite was not found.
warnings.warn("DiskDict will memory-only: "
Any ideas what is wrong here? Thanks in advance.
-- Ed

Hello,
I went through the pycuda documentation and it seems the equivalent function
is
pycuda.driver.Context.synchronize() .
Is this accurate?
I need this to block kernel calls in python, to measure kernel execution
time.
thanks
Siddharth

On Mittwoch 03 Juni 2009, Marcel Krause wrote:
> Hello Andreas, hello list,
>
> > You BOOST_PYTHON_LIBNAME is likely wrong--it refers to "gcc",
> > and you're compiling with msvc.
>
> thanks, I fixed it to "boost_python-vc90-mt". There's only a file
> "libboost_python-vc90-mt.lib" in the path I have as BOOST_LIB_DIR,
> so is the "lib" added automatically before the filename?
It is on Unix. Not sure about Windows.
> MSVC did indeed give more error messages, it was my fault that I
> used a wrong setting to redirect its output to a file. Here's the
> full error report: http://paste.nn-d.de/914 It's in german since
> I use a german version of MSVC, but maybe it helps nonetheless.
Oh my, that's all in Boost. That's good news in principle, since it's all
supposed to work--the Boost docs say it should. You're using VC 9, I take it?
http://www.boost.org/doc/libs/1_39_0/libs/python/doc/v2/platforms.html
(outdated, ick)
I think we're best advised trying to track down that syntax error first. Is
there a way of having MSVC print the include path that got it to the point
where an error occurred?
> For the siteconf.py, I'd appreciate a method to test its validity,
> e.g. try to find important files using the pathes therein, and if
> they are not found, warn me and tell me where it hat expected them
> so I can search for the file and correct the path. I could try and
> write such a verifier script if someone tells me which files are
> expected in which paths.
Oh, sweet. I'll take you up on that offer.
BOOST_INC_DIR/boost/python.hpp
BOOST_LIB_DIR/(lib)?BOOST_PYTHON_LIBNAME(.so|.dylib|?Windows?)
BOOST_LIB_DIR/(lib)?BOOST_THREAD_LIBNAME(.so|.dylib|?Windows?)
CUDA_ROOT/bin/nvcc(.exe)?
CUDA_INC_DIR/cuda.h
CUDADRV_LIB_DIR=(lib)?CUDADRV_LIBNAME(.so|.dylib|?Windows?)
Andreas

On Freitag 05 Juni 2009, Chris Heuser wrote:
> The boost warning worked. But I am confused, since I have version 1.37 of
> boost installed. I will install 1.39, but 1.37 should work, shouldn't it?
My guess here is that you installed 1.37 manually, and you also have an old
set (maybe 1.34) installed through Fedora's package management. Apparently,
the system-wide set gets picked up instead of the manually-compiled one.
Andreas

Hey everybody,
I have installed pycuda several times before, but never in Fedora (10). I
have worked my way through almost to the end, but I do not know how to get
past this error:
running build
running build_py
running build_ext
building '_driver' extension
gcc -pthread -fno-strict-aliasing -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -fPIC -O3 -DNDEBUG
-fPIC -Isrc/cpp -I/usr/include -I/usr/local/cuda/include
-I/usr/lib/python2.5/site-packages/numpy/core/include
-I/usr/include/python2.5 -c src/cpp/cuda.cpp -o
build/temp.linux-i686-2.5/src/cpp/cuda.o
In file included from src/cpp/cuda.cpp:1:
src/cpp/cuda.hpp:311: error: ‘id’ in class ‘boost::thread’ does not name a
type
src/cpp/cuda.hpp:346: error: ‘id’ in class ‘boost::thread’ does not name a
type
src/cpp/cuda.hpp: In constructor ‘cuda::context::context(CUctx_st*)’:
src/cpp/cuda.hpp:316: error: class ‘cuda::context’ does not have any field
named ‘m_thread’
src/cpp/cuda.hpp:316: error: ‘boost::this_thread’ has not been declared
src/cpp/cuda.hpp: In member function ‘void cuda::context::detach()’:
src/cpp/cuda.hpp:359: error: ‘m_thread’ was not declared in this scope
src/cpp/cuda.hpp:359: error: ‘boost::this_thread’ has not been declared
src/cpp/cuda.hpp: In constructor
‘cuda::scoped_context_activation::scoped_context_activation(boost::shared_ptr<cuda::context>)’:
src/cpp/cuda.hpp:529: error: ‘boost::this_thread’ has not been declared
src/cpp/cuda.hpp:529: error: ‘class cuda::context’ has no member named
‘thread_id’
error: command 'gcc' failed with exit status 1
[chris@chris-XPS-F pycuda]$
Any help would be greatly appreciated!
>>>Chris Heuser

On Mittwoch 03 Juni 2009, you wrote:
> Dear Andreas,
>
> thanks for the file location list. With it I was able to complete
> my siteconf.py. Attached you find my verifier script. It is tested
> only on Windows, but I think it should work on linux as well.
> Feel free to distribute it under any license you like.
Thanks for submitting this. It's now done by default at the beginning of
setup.py in git master and the 0.93 release branch.
Andreas