-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fillet of vertices in a BuildLine randomly fails #413
Comments
The first question is why are there failure rates that are anything but 100% and 0% and it seems the answer is that Now why does the order matter is another question... You can get more clever with the sorting and do |
Interestingly, the StdFail_NotDone Traceback (most recent call last)
c:\Users\someuser\script.py in line 33
42 with BuildLine() as l2:
44 add(asdf)
---> 45 fillet(l2.vertices(),.2)
46 print(f"{fail_rate=}")
50 #print(f"\npart mass = {p.part.volume*densa}")
File c:\Users\someuser\.conda\envs\ocp_vscode\Lib\site-packages\build123d\operations_generic.py:461, in fillet(objects, radius)
453 if not target.is_closed:
454 object_list = filter(
455 lambda v: not (
456 (Vector(*v.to_tuple()) - target.position_at(0)).length == 0
(...)
459 object_list,
460 )
--> 461 new_wire = target.fillet_2d(radius, object_list)
462 if context is not None:
463 context._add_to_context(new_wire, mode=Mode.REPLACE)
File c:\Users\someuser\.conda\envs\ocp_vscode\Lib\site-packages\build123d\topology.py:7011, in Wire.fillet_2d(self, radius, vertices)
6999 def fillet_2d(self, radius: float, vertices: Iterable[Vertex]) -> Wire:
7000 """fillet_2d
7001
7002 Apply 2D fillet to a wire
(...)
7009 Wire: filleted wire
7010 """
-> 7011 return Face.make_from_wires(self).fillet_2d(radius, vertices).outer_wire()
File c:\Users\someuser\.conda\envs\ocp_vscode\Lib\site-packages\build123d\topology.py:5541, in Face.fillet_2d(self, radius, vertices)
5537 fillet_builder.AddFillet(vertex.wrapped, radius)
5539 fillet_builder.Build()
-> 5541 return self.__class__(fillet_builder.Shape())
StdFail_NotDone: BRep_API: command not done |
Retested and this is fixed. It turns out it was because of a float comparison with zero issue. Closed by recent PR #515 |
Returns

~0.53
(i.e. 53% failure rate). Changing segs e.g. 3 increases the failure rate to ~77%, whereas segs=2,5,6,7,etc... seem to have a 0% failure rate. This may be related to other issues already filed.The text was updated successfully, but these errors were encountered: