Opened 19 years ago
Last modified 18 years ago
#23 closed defect
bad mesh generated. — at Version 1
Reported by: | duncan | Owned by: | somebody |
---|---|---|---|
Priority: | normal | Milestone: | Mesh generation maintenance |
Component: | Functionality and features | Version: | 1.0 |
Severity: | normal | Keywords: | |
Cc: | duncan |
Description (last modified by duncan)
This is from ticket #9, which was overloaded.
here's an error from least-squares.py
v 6 self.mesh.vertexlist[v] None Traceback (most recent call last): File "I:\inundation\debug\mesh_error_reporting\show_mesh_bug.py", li ne 123, in ? verbose=True) File "I:\inundation\pyvolution\least_squares.py", line 211, in fit_t o_mesh precrop = precrop) File "I:\inundation\pyvolution\least_squares.py", line 360, in __ini t__ precrop = precrop) File "I:\inundation\pyvolution\least_squares.py", line 545, in build _interpolation_matrix_A element_found, sigma0, sigma1, sigma2, k = \ File "I:\inundation\pyvolution\least_squares.py", line 608, in searc h_triangles_of_vertices for k, _ in self.mesh.vertexlist[v]: TypeError: iteration over non-sequence
It's caused since vertex 6 is not part of any triangle.
I:\inundation\debug\mesh_error_reporting\show_bad_mesh.py (changeset:1954)produces a different mesh that shows the same error. Vertex 10 is not associated with any triangle. This is evident in the .tsh file.
See show_mesh_bug.py (changeset:1878) for 1st report of bug.
Currently least squares assumes a mesh is ok. Should this be changed? probably.
Change History (1)
comment:1 Changed 19 years ago by duncan
- Description modified (diff)
- Summary changed from crash when generating a mesh to bad mesh generated.
Note: See
TracTickets for help on using
tickets.