Segmentation fault when loading semanticKITTI dataset

[jbehley]

Segmentation fault when loading semanticKITTI dataset

[jbehley]

As I said, it's unlikely that it's a problem with the files, but with the graphics driver.

It might be that I'm using somewhere a feature which is not required by the specification of the core profile of OpenGL. Therefore, it says "invalid enumerant". Nvidia drivers are less picky and silently accept also some non-core functions, texture types, etc. but finding this is really hard for me, since I use a Nvidia GPU with nvidia drivers.

Thus my suggestion to try with proper graphics drivers.

[jbehley]

It seems that the OpenGL driver has some problems. It might be better to use a native graphics driver provided by the vendor of the graphics card.

The folder structure should be the same as described here: https://github.com/jbehley/point_labeler#folder-structure

The pose files that we provide with the dataset are the ones that we used to annotate the data; these poses also include loop closures.

[fredpeertje]

So, the poses.txt files are not the ones provided in this zip? http://www.cvlibs.net/download.php?file=data_odometry_poses.zip Where can I download the poses.txt files? I tried the SuMA tool to create them but got the same issue as described here: jbehley/SuMa#16 (comment)

[jbehley]

We used our Surfel-based Mapping approach to perform mapping and loop closures (some loop closures were manually tagged). Therefore, our poses will have consistent poses when revisiting areas, which are not provided by the GPS/INS poses.

The poses are included in our SemanticKitti release: http://semantic-kitti.org/dataset.html#download

Regarding the save dialog issue, I can unfortunately not reproduce the error. I never tested my software in VMWare and cannot provide any support for this.

[fredpeertje]

Ah the poses.txt files are in this zip file http://www.semantic-kitti.org/assets/data_odometry_labels.zip. Unfortunately same error, segmentation fault.

[jbehley]

Since there is no activity since some time, I close this issue now. If you have further comments on this issue, you can reopen it. Thanks.