Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem using visualize.py #151

Open
Shiyao-Xu opened this issue Jun 27, 2024 · 2 comments
Open

Problem using visualize.py #151

Shiyao-Xu opened this issue Jun 27, 2024 · 2 comments

Comments

@Shiyao-Xu
Copy link

Shiyao-Xu commented Jun 27, 2024

Dear Team,

thank you for your work! I'm currently using this api for occupancy prediction task, and now facing with one fatal question. When I tried to launch visualize.py file, I got this output in terminal:

`********************************************************************************
INTERFACE:
Dataset ../semantic_KITTI/kitti/
Config config/semantic-kitti.yaml
Sequence 00
Predictions None
ignore_semantics False
do_instances False
ignore_images False
link False
ignore_safety False
color_learning_map False
offset 0


Opening config file config/semantic-kitti.yaml
Sequence folder ../semantic_KITTI/kitti/sequences/00/velodyne exists! Using sequence from ../semantic_KITTI/kitti/sequences/00/velodyne
Labels folder ../semantic_KITTI/kitti/sequences/00/labels exists! Using labels from ../semantic_KITTI/kitti/sequences/00/labels
Using semantics in visualizer
To navigate:
b: back (previous scan)
n: next (next scan)
q: quit (exit program)
/media/varda/Dolphin/miniconda3/lib/python3.12/site-packages/vispy/gloo/texture.py:364: UserWarning: GPUs can't support dtypes bigger than 32-bit, but got 'float64'. Precision will be lost due to downcasting to 32-bit.
data = downcast_to_32bit_if_needed(data, copy=copy)`

No ERROR occurred, but no vis window either...

Could you please help me with this problem? Is it because my GPU performance is too low(1080Ti)?

Best,
Shiyao

@jbehley
Copy link
Member

jbehley commented Jun 28, 2024

thanks for your interest in our work: I suspect that it has nothing to do with the GPU as it's only visualizing the point clouds; but I haven't checked in a while if the code still works with newer python packages. I guess that the error message from vispy has something to do with this. It might be that you have to use an earlier vispy version?

I have to look into this, but I will only possibly have time to look into this at earliest next week.

@chadrs2
Copy link

chadrs2 commented Aug 28, 2024

I got the exact same error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants