-
Notifications
You must be signed in to change notification settings - Fork 29
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
index out of bounds #2
Comments
Hi,Did you solved this problem? |
The 'Index out of bound' error happened because torch.topk sometimes crashed in ill conditions. Actually the error happened in function get_graph_feature: Replacing topk with sort seems to be stable. |
That's a great observation! Thanks for the suggestions! |
when I replaced topk with sort, I encountered a new problem: Traceback (most recent call last): I still don't know how to solve it.... |
That lapack error means that your matrix H is ill-conditioned. A simple fix is adding an identity matrix with some scaling values ( |
After having replaced topk with sort, I now got this error:
This is traced back to
|
The traceback of a cuda error can be inaccurate sometimes. A general approach to debug this type of errors is firstly setting CUDA_LAUNCH_BLOCKING=1 when running your program. In this way you can get a more accurate traceback location. Then you can raise an exception at the traceback location to help you catch the invalid index and figure out what happened during training. Hope this can help you. |
@lu-ming-lei hi, I think it's due to your torch version, it seems some torch versions have unstable torch.svd() behavior, especially when the covariance matrix is ill-conditioned. You can install pytorch1.0.1, this works for me. |
This is to confirm pytorch1.0.1 work for me and I'll close this issue. Feel free to reopen it if it doesn't work. |
@wangyujiewj
|
There was an error called "index out of bounds" when I ran the code.
The text was updated successfully, but these errors were encountered: