brep.m_L loop is not valid.
end of brep.m_T[loop.m_ti=5]=(16.3982,0.000628564) and start
of brep.m_T[loop.m_ti=6]=(16.3982,0.000269198) do not match.
brep.m_F face is not valid.
brep.m_L[face.m_li=0] is not valid.
ON_Brep.m_F is invalid.
How was this bad object created?
Also, in your script, rs.GetObject will return the id of a Brep object. So you want your script do look something like this:
import rhinoscriptsyntax as rs
import scriptcontext as sc
uuid = rs.GetObject("Select surface", rs.filter.surface, preselect=True)
if uuid is None: return
brep = rs.coercebrep(uuid)
srf = brep.Faces.UnderlyingSurface()
if __name__ == '__main__': main()
I am creating a script that repairs/reconditions breps. I want all of the work to be done to the Geometry.Brep before replacing the original DocObjects.BrepObject. Unfortunately, here is an example where the geometry of the revised DocObjects.BrepObject does not match the Geometry.Brep used to create it.
The trim error that the log is reporting is not directly related to why multiple surfaces are added. This can be demonstrated by:
_Untrim(ming) the brep. The untrimmed brep is valid.
Run the script on the untrimmed . Again, a polysurface is created.
It seems that SplitKinkyFaces() is automatically called before the brep is added to the document. Is this what is happening?
I was working on a brep modification script, but in order for it to be more successful, had switched my focus to brep repair/reconditioning, e.g., removing thin faces. Today, I was working on scripting the repair of invalid faces and discovered this behavior of AddSurface().
Some points are close to one another, not stacked. There are 2 kinks in the surface though.