You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Markusjsommer, I just got Balrog killed while running it on GPU with no further error message. It said the process was killed and that was it. Is there a way to enable a more verbose error output? It was killed after looking at 49 scaffolds.
Thanks!
Edit: I've re-run Balrog on the same machine using a smaller batch size but also real-time monitoring the process and can now say that this was killed because of RAM issues. It used up all the RAM available in my machine until it got killed (at 49 scaffolds as well). Any help?
The text was updated successfully, but these errors were encountered:
Hi @Markusjsommer, I just got Balrog killed while running it on GPU with no further error message. It said the process was killed and that was it. Is there a way to enable a more verbose error output? It was killed after looking at 49 scaffolds.
Thanks!
Edit: I've re-run Balrog on the same machine using a smaller batch size but also real-time monitoring the process and can now say that this was killed because of RAM issues. It used up all the RAM available in my machine until it got killed (at 49 scaffolds as well). Any help?
The text was updated successfully, but these errors were encountered: