You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm new to 3D reconstruction and I want to know how to visualize the seg.npy in the logs folder. I have successfully visualized other npy documents but when it came to the seg.npy document, I ran into error information.
The text was updated successfully, but these errors were encountered:
Hi @zw20130717! If you would like to visualize the segmentation map, you need to convert the segmentation maps to 3 channels (RGB for 3 channels). The reason why the seg.npy files cannot be directly visualized is because it is now 13 channels (as you can see from the error message of the tensor shape being (480, 640, 13)). You could either map the semantic class manually using a (13, 3) mapping table, with each row being the RGB color for each semantic class, or use some existing functions like those in matplotlib https://matplotlib.org/stable/users/explain/colors/colormaps.html to map the discrete class indices to RGB colors.
Hi @zw20130717! If you would like to visualize the segmentation map, you need to convert the segmentation maps to 3 channels (RGB for 3 channels). The reason why the seg.npy files cannot be directly visualized is because it is now 13 channels (as you can see from the error message of the tensor shape being (480, 640, 13)). You could either map the semantic class manually using a (13, 3) mapping table, with each row being the RGB color for each semantic class, or use some existing functions like those in matplotlib https://matplotlib.org/stable/users/explain/colors/colormaps.html to map the discrete class indices to RGB colors.
You've been such helpful! Thank you for your reply!
Hi, I'm new to 3D reconstruction and I want to know how to visualize the seg.npy in the logs folder. I have successfully visualized other npy documents but when it came to the seg.npy document, I ran into error information.
The text was updated successfully, but these errors were encountered: