Open rkdckddnjs9 opened 11 months ago
Even if the evaluation was conducted on another server with 128G of RAM, it was confirmed that the memory was exceeded.
Even if the evaluation was conducted on another server with 128G of RAM, it was confirmed that the memory was exceeded.
Have you solved this? The memory overflow on the 160g RAM too.
Even if the evaluation was conducted on another server with 128G of RAM, it was confirmed that the memory was exceeded.
Have you solved this? The memory overflow on the 160g RAM too.
I tried several methods, but couldn't solve it.
This work preserves the history information in the RAM, so more memory is needed.
This work preserves the history information in the RAM, so more memory is needed.
Could you give me your computer specifications and environmental information?
This work preserves the history information in the RAM, so more memory is needed.
Could you give me your computer specifications and environmental information?
I run the code on the cluster, similar errors occur when I specify the default quantity memory, but this problem is solved when I allocate 500g memory.
This work preserves the history information in the RAM, so more memory is needed.
Could you give me your computer specifications and environmental information?
I run the code on the cluster, similar errors occur when I specify the default quantity memory, but this problem is solved when I allocate 500g memory.
Thank you for your reply :)
Thanks for your excellent works!
When I test with dist_test.sh, the memory continues to increase, causing the evaluation to stop. The same thing happens when fbocc.py's pred_occcupancy_category = pred_occcupancy_category.cpu().numpy() is performed without changing to cpu. I wonder if there were any problems like this, do you know how to solve them?