Skip to content
#

cuda

Here are 1,984 public repositories matching this topic...

r4nt
r4nt commented Jun 25, 2018

The problem as far as I understand is that libfoo.so's only knowledge about libcuda.so is its SONAME, which is libcuda.so.1, so a binary wanting to link in libfoo.so needs to know who to find libcuda.so.1 in order to verify the available symbols. Generally, ld's suggestion is to use -rpath-link to provide the path to the library, but the nvidia docker repository doesn't come with the symlink to li

itaipee
itaipee commented Dec 31, 2018

low priority issue , it is not a real issue to debug this error , and install bc afterwards , but nevertheless , this is not a native linux command . you should add some warning in , maybe in run.sh for all the diarizations recipe , or in the script itself.

https://github.com/kaldi-asr/kaldi/blob/3e77220b3297831c3a370169580b880461897682/egs/callhome_diarization/v1/diarization/extract_ivecto

jrhemstad
jrhemstad commented Jul 10, 2019

Is your feature request related to a problem? Please describe.
According to the Arrow spec:

Bitmaps are to be initialized to be all unset at allocation time (this includes padding).

This would imply that bits outside the range [0, size) should always be zero. However, in cuDF/libcudf, we take a more conservative approach and say that bits outside [0,size) are undefined in order to a

dantegd
dantegd commented Dec 7, 2019

Describe the bug
The target clean of the root build.sh script should clean all build artifacts of a build made with the standard names and folder paths. Currently it erases almost everything, but fails to delete the cythonized files of the .pyx source files, like python/cuml/cluster/dbscan.pyx. The script should erase those artifacts as well to trigger a "re-cythonization" of all file

cciccole
cciccole commented Jun 14, 2019

The Python API has a random_seed attribute for the tsnecuda.TSNE class but it's ignored.

Random seed is tracked as an option within the tsnecuda implementation but it looks hard coded to time-based seed instead. Is there a good reason for this?

I might implement and PR this change unless you indicate otherwise or do it first.

Improve this page

Add a description, image, and links to the cuda topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the cuda topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.