-
Notifications
You must be signed in to change notification settings - Fork 148
Description
hi, thanks for the fantastic work.
I met the similar problem like #21.
I did according to the REAME.md, the only difference is that I added two CMake parameters as below, so that there would not be "out of memory" error on my GPU ( Nvidia 840M, yes... an old one)
-DMASKFUSION_NUM_GSURFELS=921600 -DMASKFUSION_NUM_OSURFELS=102400
and checked my toml file to keep it unchanged:
# If not empty, ignore every class not listed here. Example: ['teddy bear']
filter_classes = []
# If not empty, only track classes listed here (otherwise apply BG motion)
trackable_classes = []
# Reject predictions with lower score
score_threshold = 0.55
However, when running on the dataset from Co-Fusion, it seems the label "clock" has been filtered.
so in the final result, the trajectory of the clock makes the reconstruction not so good:
The offline result from MaskRCNN shows good:
I'm wondering why the dynamic parts are ignored and not tracked. Is there some size filter somewhere else? My output shows like below:
Initialised multi-object fusion (main-thread: 140037120672128)
- The background model can have up to 921600 surfel (960x960)
- Object models can have up to 102400 surfel (320x320)
- Using GPU 0 for SLAM system and GPU 0 for MaskRCNN
- Using frame-queue of size: 0
New label detected (**2147483647,2147483647 -2147483648,-2147483648**) - try relocating...
Found new model.
Created model with max number of vertices: 102400
New label detected (2147483647,2147483647 -2147483648,-2147483648) - try relocating...
Found new model.
Created model with max number of vertices: 102400
"2147483647,2147483647 -2147483648,-2147483648" is a little weird, however I checked the codes and they are defined as initial values for bounding boxes.
Thanks so much. I'll keep on digging into the codes to find the answer.