Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error when using af.set_backend('cuda')

Open
#202 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reproducing the reported af.set_backend('cuda') failure and compare af.info() and af.get_backend() with the reported CPU-only output. Inspect the Python package's backend-loading and installation entry points; done means a correctly installed CUDA-capable environment exposes the CUDA backend or the missing requirement is documented clearly.

Written by the indexing model from the issue text.

Description

When I try to switch backend using af.set_backend('cuda'), I got error like:

report

It seems that I do not have cuda devices as candiated backend although I have 8 gpus in fact, and the output of af.info()

In [2]: af.info()
ArrayFire v3.6.2 (CPU, 64-bit Linux, build dc38ef1)
[0] Intel: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz, 257588 MB, Max threads(44) 

and af.get_backend()

In [2]: af.get_backend()
Out[2]: 'unified'

So does I missing something when installing the package?

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arrayfire/arrayfire-python

All issues in arrayfire/arrayfire-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.