Open francisr opened 7 years ago
Any update?
Sorry, I completely missed this one :( Could you please provide the data on which I can reproduce the problem - apparently the code works for me.
As a workaround, try setting yinyang_t
to 0.
It's hard to provide an example as this error doesn't always occur, I'll see what I can get.
Would setting yinyang_t
to 0 incur any accuracy penalty?
No accuracy penalty, 1.5x speed decrease in the worst case.
Hi! I managed to (kind of) reproduce the issue. The files attached are the minimal steps required to produce the error. However, it only occurs for around 20% of the times. I am using a machine with two GTX TITAN X, and this program crashes in both of them. This is running 6.2.1 version.
OK, I am reproducing the bug this week, thanks for posting.
Sorry, I completely missed this one :( Could you please provide the data on which I can reproduce the problem - apparently the code works for me.
As a workaround, try setting
yinyang_t
to 0.
hello,I want to know What does this parameter ‘yinyang_t’mean?
hello! I occer this bug today yet. any update here? Thanks a lot!
I have a
cudaMemcpy failed
that pops up randomly when my init isk-means++
. Full log: