Benedikt Mersch

Hi @E4CEeg, Did you verify that your annotated data is correct? One way to check would be to use the visualizer of the [SemanticKITTI API](https://github.com/PRBonn/semantic-kitti-api). You can also use this...

Did you find any problem on our side? Otherwise, I would close this issue since it seems to be related to the point labeling rather than the 4DMOS code.

Which labels are you using for annotation? It should definitely work predicting moving objects with the pre-trained ```10scans.ckpt``` model on sequence 11 and visualizing them with the SemanticKITTI API. Can...

By running ```visualize.py```, you are using the semantic segmentation config of SemanticKITTI and not the MOS config file. The problem is the wrong label mapping since moving objects are labeled...

> The custom region has not been ported to v0.5 yet. Sorry for the delay. I'll try to finish it in a few weeks. Hi @chrischoy, Can you give an...

Hi, I was able to use the ```RegionType=HYBRID``` with ME version 4.3. However, a lot of other functionalities are not available here, therefore I would like to use the hybrid...

Note that the points that are passed to the `integrate` function need to be in a common frame. Is that the case on your side?

These should be the transformed points and the poses in the same coordinate frame. So, if you have transformations from each local frame to the base frame, pass those poses...

What exactly is your base frame representing? How are you aligning the points? Can you maybe share the point clouds with us for testing? First looking at this, (Aligned**P**. Base**T**Local)...

Hey, I am happy to hear that the code will finally be released soon. @vivonicole, if you search for additional baselines for comparison, you can also check out our point...