You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warning safe to ignore? "Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support"
#555
In my Activity Monitor, it now shows GPU % below and in R-Studio, it shows below.
Does that means it is working, even though the warning "Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support" is still there?
The text was updated successfully, but these errors were encountered:
denvercal1234GitHub
changed the title
Error using Tensorflow in R-Studio: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at xla_ops.cc:418 : NOT_FOUND: could not find registered platform with id
Error using Tensorflow in R-Studio: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at xla_ops.cc:418 : NOT_FOUND: could not find registered platform
Jan 30, 2023
denvercal1234GitHub
changed the title
Error using Tensorflow in R-Studio: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at xla_ops.cc:418 : NOT_FOUND: could not find registered platform
Warning safe to ignore? "Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support"
Mar 22, 2023
Hi there,
After reinstalling miniforge, I activated tensorflow env with conda (https://gist.github.com/juliasilge/035d54c59436604d6142ebebf29aa224), then train a neural net using tensorflow in R-Studio for the package
infinityFlow
(ebecht/infinityFlow#13).In my Activity Monitor, it now shows GPU % below and in R-Studio, it shows below.
Does that means it is working, even though the warning "Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support" is still there?
Thank you for your help!
Related #530 #532
The text was updated successfully, but these errors were encountered: