-
Notifications
You must be signed in to change notification settings - Fork 18
oom error #27
Comments
Hi @zoepiran , would you mind shrinking down your code to a minimal example and paste it here? It would be much easier to track down the bug. Also I believe you can probably replace your data by random data, if the error is memory, the problem most likely linked to the amount of data, not the actual values. |
Hi Zoe, I agree with Olivier that a working colab should be easier for us to parse. In the meantime, maybe you could help me parse the log files. In
but I can't see immediately where the |
Here;
|
its missing in the |
I suspect the issue lies in this
here We might be able to come up with an efficient implementation of this for squared Euclidean distance, but at this point I would suggest directly rescaling the entry vectors in additionally.. we just removed the |
Excuse my delay; created the following colab |
hi,
Please excuse me in advance if there is a basic mis-usage in the attached code/setting.
In this drive you can find the following folders:
[1]
code
: two code files (differing in the cost object type, in 'gwlr.py' costs arepointclouds
and ingwlr_geom,py
we use generalGeometry
) which can reproduce ouroom
errors we encounter running on GPUs.** we noticed that changing
alpha
to0.75
we are able refrain fromoom
usinglow rank
however while geometry run returned quickly the pointcloud calculation took >2 hrs.[2]
logs
: 4 log-files documenting the errors in regular (quad
) and low rank (lr
) runs usingpointcloud
costs andGeometry
(geom
) objects.[3]
data
: The data to run the code.We realize it may be that the data is too large but will be grateful for your input.
(I am still trying to set-up different mem. allocation on our GPUs that may allow this)
Thank you in advance :)
The text was updated successfully, but these errors were encountered: