JIT issues when using jupyter notebook
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing af.gaussian_kernel(128,128,5,5) in the reported Jupyter and IPython environments, then trace the failure through arrayfire/image.py and arrayfire/util.py into src/backend/cuda/jit.cpp. Done means the call works in Jupyter under the reported setup, with the CUDA JIT error understood or prevented.
Written by the indexing model from the issue text.
Description
Hi, after updating to the latest arrayfire jupyter notebook seems to have a problem with af.gaussian_kernel() function. Standard ipython works without a problem but in notebook the call ends up with:
RuntimeError Traceback (most recent call last)
<ipython-input-3-e9e47878ee5a> in <module>()
----> 1 lala = af.gaussian_kernel(128,128,5,5)
~/anaconda3/lib/python3.6/site-packages/arrayfire/image.py in gaussian_kernel(rows, cols, sigma_r, sigma_c)
778 safe_call(backend.get().af_gaussian_kernel(c_pointer(out.arr),
779 c_int_t(rows), c_int_t(cols),
--> 780 c_double_t(sigma_r), c_double_t(sigma_c)))
781 return out
782
~/anaconda3/lib/python3.6/site-packages/arrayfire/util.py in safe_call(af_error)
77 err_len = c_dim_t(0)
78 backend.get().af_get_last_error(c_pointer(err_str), c_pointer(err_len))
---> 79 raise RuntimeError(to_str(err_str))
80
81 def get_version():
RuntimeError: In function std::vector<char> cuda::compileToPTX(const char*, std::string)
In file src/backend/cuda/jit.cpp:
I tried complete reinstall of python, cleaned any personal settings in .local .bashrc .config and installed completely new anaconda. Still whatever I do I cant get it to run
NOTE: af.constant() function works without problem
SYSTEM: ubuntu 17.10; CUDA 9-2; arrayfire v3.6 binary; arrayfire-python git master
- Dominant language
- Python
- Stars
- 422
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from arrayfire/arrayfire-python
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
arrayfire/arrayfire-python#271 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
arrayfire/arrayfire-python#270 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
arrayfire/arrayfire-python#269 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
arrayfire/arrayfire-python#268 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
arrayfire/arrayfire-python#267 · 1 comment · 1 reaction ·
All issues in arrayfire/arrayfire-python
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·