`chainer.get_device(10)` does not cause error
See original GitHub issueTesting under chainer==6.0.0 with chainerx built and cupy installed. Testing environment has only 1 GPU.
import chainer
device = chainer.get_device(10) # NOT Cause error!
print('device', device) # @cupy:10
device2 = chainer.get_device('cuda:10') # Cause error!
print('device2', device2)
When we try to get GPU device with id more than allowed, the behavior is different between cupy & chainerx cuda device.
- cupy: does not raise error
- chainerx cuda: raise error
I think raising error is more convenient for users. How do you think?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (9 by maintainers)
Top Results From Across the Web
cudaErrorNoDevice: no CUDA-capable device is detected ...
I am using AWS p3 type 2xlarge instance type with following GPU details: root@awsml04:~# nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright...
Read more >failure to create a DirectX device and swapchain - c++
DXGI Error: IDXGIFactory::CreateSwapChain: SwapEffect is unknown. which I am guessing I did not add the swapeffect attributes. I will do that ...
Read more >Configuration problems:xcf32p been configuration sucessfylly with ...
using boundary scan mode,I initialized my jtag chain,and found xcf32p,then program sucessfully. right click xcf32p,blanck check,get device ...
Read more >Handle device removed scenarios in Direct3D 11
This topic explains how to recreate the Direct3D and DXGI device interface chain when the graphics adapter is removed or reinitialized.
Read more >Best practices for unique identifiers - Android Developers
Best practices for working with Android identifiers; Work with advertising IDs; Work with FIDs and GUIDs; Don't work with MAC addresses.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
#7486 correct the pickle behavior by re-creating the lock when the object is deserialized.
This issue is closed as announced. Feel free to re-open it if needed.