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
I don't know exactly which of the two buttons I clicked triggered an error, but I stumbled upon a singular matrix error that was unhandled, when manually moving the 3D view map.
To reproduce
Enable 3d view
Add maps (I had raster and vectors) from the data box
Click on the rotate 3D scene tool (orange 4 arrows), OR the zoom to map, then play around the map
See error in the console tab
Expected behavior
Inverting a matrix can happen to hit a singular matrix, we can't beat the maths on this. I did not expect to have it unhandled and have a long traceback in the console window though. Could we be handling this better?
When working on nviz/3D view gui code recently, I saw that there were some warnings suggesting to use plain ndarrays instead of the "matrix" object we use there. It will probably not fix the math issue though.
The text was updated successfully, but these errors were encountered:
Describe the bug
I don't know exactly which of the two buttons I clicked triggered an error, but I stumbled upon a singular matrix error that was unhandled, when manually moving the 3D view map.
To reproduce
Expected behavior
Inverting a matrix can happen to hit a singular matrix, we can't beat the maths on this. I did not expect to have it unhandled and have a long traceback in the console window though. Could we be handling this better?
Screenshots
The saved log:
grass_cmd_output.txt
In text here to help for searches:
Details
System description
Operating System: Windows 11 24H2 26100.2605
GRASS GIS version: 8.5 dev, from osgeo4w grass-dev 8.5-435-68a51f64a-1 for 68a51f6
details about further software components
Additional context
When working on nviz/3D view gui code recently, I saw that there were some warnings suggesting to use plain ndarrays instead of the "matrix" object we use there. It will probably not fix the math issue though.
The text was updated successfully, but these errors were encountered: