topic Re: API bug in ElementIntersectsElementFilter in Revit API Forum

API bug in ElementIntersectsElementFilter

Anonymous — Fri, 02 Jun 2017 21:08:02 GMT

Hi there,

During development I found that the Revit API ElementIntersectsElementFilter fails on finding the intersection between the rebar and Beam(T-Girder) FLAT member at some specific positions.

I have attached the model(2016), .addin and .dll file.

Hope someone can help me with this issue.

Thank you!

Best,

Siwan

Re: API bug in ElementIntersectsElementFilter

Revitalizer — Tue, 06 Jun 2017 06:46:34 GMT

Hi,

in the RevitAPI.chm, on the ElementIntersectsElementFilter page, it says:

"[...] Also, elements which have no solid geometry, such as Rebar, will never be detected as intersecting by this filter."

It's not a bug.

Revitalizer

Re: API bug in ElementIntersectsElementFilter

Anonymous — Tue, 06 Jun 2017 13:00:28 GMT

Hi Revitalizer,

If you open the project, you can see that it's not a Revit Rebar, it's a customer family and it has solid geometry.

Thank you for your help.

Best,

Siwan

Re: API bug in ElementIntersectsElementFilter

Revitalizer — Tue, 06 Jun 2017 14:04:55 GMT

Hi,

I've opened your Revit file but cannot tell you why the Filter does not function.

Since you did provide the dll but none of the code, there are no other hints.

Sorry, no idea.

Revitalizer

Re: API bug in ElementIntersectsElementFilter

FAIR59 — Tue, 06 Jun 2017 15:01:21 GMT

the beam family has no geometry defined (geometry is part of the nested shared family). so nothing intersects with the beam.

Re: API bug in ElementIntersectsElementFilter

Anonymous — Tue, 06 Jun 2017 15:42:30 GMT

Hi,

I am actually looking for the intersection between the "FLAT" (nested) member of that beam and the custom rebar family (specialty equipment) so I think both of them have family geometry. Also if you move the rebar to other places the function would return that they're intersected.

I've attached the code. Thanks!

Re: API bug in ElementIntersectsElementFilter

Anonymous — Tue, 06 Jun 2017 15:46:11 GMT

Hi, I've attached the code in the screen shot for you to see if it helps.

I am looking for the intersection between the "FLAT" (nested) member of that beam and the custom rebar family (specialty equipment), and it works in most intersection places but not the position that I put the rebar on.

Thanks!

Re: API bug in ElementIntersectsElementFilter

Anonymous — Tue, 06 Jun 2017 15:47:17 GMT

Please see attached file

Re: API bug in ElementIntersectsElementFilter

FAIR59 — Tue, 06 Jun 2017 21:55:35 GMT

on analysing the nested families, I noted that the path of the Warped family is a part of a very large circle. So the host face of the rebar-family is ever so slightly non horizontal. So you're entering into areas of numerical imprecision when dealing with pointy things, slightly of axis elements and things like that. So the bug is not a bug of the filter, but a "bug" of imperfect calculation.

If you replace the swept-path with a straight line, the Flat-family will find the intersection with the rebar family.

Re: API bug in ElementIntersectsElementFilter

Anonymous — Wed, 07 Jun 2017 15:01:35 GMT

Looks like the case. The radius is 29999' 11 7/8" and with single precision values we basically get about 6-7 digits of precision so 29999.9895833333 which probably gives us a resulting 29999.98 (roughly) and the rebar 1/2 diameter is 0.015625' so it's pretty close to the murky region.

The consternation is that it isn't a failed intersection all over the piece, only at certain locations so in calculating it must just be random enough, in terms of floating point rounding, that it works sometimes and not others. I would like to see it a little more consistently failing at the middle of the element (where the camber delta is greatest and not at the end where the camber delta is not) but as it's really rounding precision error it's probably too much to ask.

If, however, Revit is working in double precision then this is a legit bug, even with the bar hosted to the warped element.