Changes between Initial Version and Version 1 of Ticket #23


Ignore:
Timestamp:
Oct 18, 2005, 9:59:55 AM (20 years ago)
Author:
duncan
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #23

    • Property Summary changed from crash when generating a mesh to bad mesh generated.

  • Ticket #23 – Description

    initial v1  
    11This is from ticket #9, which was overloaded.
    22
    3 Currently the only details of this error are:
     3here's an error from least-squares.py
    44
    5 See show_mesh_bug.py (changeset:1878)
     5{{{
     6v 6
     7self.mesh.vertexlist[v] None
     8Traceback (most recent call last):
     9  File "I:\inundation\debug\mesh_error_reporting\show_mesh_bug.py", li
     10ne 123, in ?
     11    verbose=True)
     12  File "I:\inundation\pyvolution\least_squares.py", line 211, in fit_t
     13o_mesh
     14    precrop = precrop)
     15  File "I:\inundation\pyvolution\least_squares.py", line 360, in __ini
     16t__
     17    precrop = precrop)
     18  File "I:\inundation\pyvolution\least_squares.py", line 545, in build
     19_interpolation_matrix_A
     20    element_found, sigma0, sigma1, sigma2, k = \
     21  File "I:\inundation\pyvolution\least_squares.py", line 608, in searc
     22h_triangles_of_vertices
     23    for k, _ in self.mesh.vertexlist[v]:
     24TypeError: iteration over non-sequence
     25}}}
     26It's caused since vertex 6 is not part of any triangle.
    627
    7 I think it's a mesh gen problem.
     28I:\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.
     29
     30
     31
     32See show_mesh_bug.py (changeset:1878) for 1st report of bug.
     33
     34Currently least squares assumes a mesh is ok. 
     35Should this be changed?  probably.