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 BlenderProc team. I've been wanting to use blenderproc for some of my dev teams machine learning pipelines, and it runs great locally on an Ubuntu 20.04 instance. However, we wanted to make it easier to use collaboratively for our entire team, so we decided to run blenderproc in google colab. However we are getting the following logs for the cell:
Note that ! indicates we are executing a linux command . This executes in a temporary shell.
@mshunjan Hi, for running Blender inside Colab, you need to reinstall libtcmalloc, install some additional packages (assuming if they are not installed already) and set the LD_PRELOAD env variable as shown below. Please run these commands before the run.py call. Let me know if this resolves your issue?
Hi @moizsajid! Thanks this worked for me. Looks like I was missing the libtcmalloc library. I'll close the issue, now. For anyone that stumbles across this in the future, here's what my code looked like to solve this:
%cd/content/
!gitclonehttps://github.com/DLR-RM/BlenderProc.git# Download some required librariesimportos
!aptinstalllibtcmalloc-minimal4os.environ["LD_PRELOAD"] ="/usr/lib/x86_64-linux-gnu/libtcmalloc_minimal.so.4.3.0"
!aptinstalllibboost-all-dev
!aptinstalllibgl1-mesa-dev
I also had to manually install these pip dependencies for plotting, however this is unrelated to the issue. This is what I did:
Hi BlenderProc team. I've been wanting to use blenderproc for some of my dev teams machine learning pipelines, and it runs great locally on an Ubuntu 20.04 instance. However, we wanted to make it easier to use collaboratively for our entire team, so we decided to run blenderproc in google colab. However we are getting the following logs for the cell:
Note that ! indicates we are executing a linux command . This executes in a temporary shell.
logs:
We think it is a problem with line 278 in run.py
The text was updated successfully, but these errors were encountered: