isl-org / isl-org/Open3D

Reconstruction system with Intel Realsense D435

Open
#6,056 0 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
C++
Stars
14k
Forks
2.6k
Avg merge
5d 18h
Merged PRs (30d)
6

Description

### Checklist

- [X] I have searched for [similar issues](https://github.com/isl-org/Open3D/issues).
- [X] For Python issues, I have tested with the [latest development wheel](http://www.open3d.org/docs/latest/getting_started.html#development-version-pip).
- [X] I have checked the [release documentation](http://www.open3d.org/docs/release/) and the [latest documentation](http://www.open3d.org/docs/latest/) (for `master` branch).

### My Question

I need to make the reconstruction with a custom dataset from intel realsense D435. I have already used the [realsense_recorder.py](https://github.com/isl-org/Open3D/blob/master/examples/python/reconstruction_system/sensors/realsense_recorder.py) to get the data.
1- When I use the reconstruction system, make_fragements I got this error when I use the **joblib** as **MAX_THREAD**
but when I put the n_jobs to 2 it works fine but took too much time
![Screenshot from 2023-04-02 17-15-25](https://user-images.githubusercontent.com/74091020/229760737-9e335507-1643-4282-95fc-628f2970be2e.png)

2- When I use the reconstruction system I got this "**Killed**" in the integration step and I have read that this means out of memory but I have already alot of memory in my laptop.
![WhatsApp Image 2023-04-04 at 12 37 22 PM](https://user-images.githubusercontent.com/74091020/229766716-56415bc5-52d6-4543-8b01-6b487c496c94.jpeg)

3- Also, when I run the reconstruction system it took almost all the RAM ans swap memory. Is this behaviour ok with open3d or is there something wrong I should do?

> - Operating system: Ubuntu 18.04
> - Python version: Python 3.8.10
> - Open3D version: 0.13.0

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.