-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs about reading symmetric mtx data and processing data #5
Comments
Hi @wyatuestc, I tried on the latest commit from
Could you doublecheck you were on the latest |
Hi Carel,
Thanks! |
Hi @wyatuestc, thanks I confirmed that this is indeed a bug. It should be fixed in the new commit c147935. The reason is that as pointed out in this issue, the code will filter out the self-loops (i.e. elements on the diagonal). However, the bug caused it to fail to do so if the diagonal nonzero happened to be the
As pointed out in the issue, if you don't want it to filter out diagonal elements, you will have to set to false Line 220 in 5b84296
Then the result will be the same as the general case:
|
Thanks! |
I've tested on Volta and Pascal and it works, but have not tested Turing. It should work for Turing in theory, or at least with minimal modification. |
Thanks! I'm running gspmm on RTX2080 (Turing).
command: ./bin/gspmm --debug=true --mode="mergepath" ./[matrix].mtx data: |
Sorry for the slow response. Thank you so much for bringing this to my attention, Yang! I tried your datasets, and 4 x 32/1024 x 1024 are indeed wrong. I tested on Tesla V GPU with 12GB memory. I tracked down the 4 x 32 error to an incorrect assumption in the test file Need some more time to investigate 1024 x 1024 error. |
Hi @YangWang92, thanks for pointing out the error. If you use the command: Still investigating why this value for |
Hi all, I found a bug in reading symmetric mtx data.
For example, when I tried to run
to read 4x4 dense matrix from 4_4coo_dense.mtx.
It will load a broken matrix from the symmetric mtx.
Wrong results
Correct Results
The text was updated successfully, but these errors were encountered: