Room / Space intersecting Mechanical elements & space information

[sanjaya]

Hi,

I have developed a script to get the information of mechanical elements which are intersecting with the space created. However, I can get the solids created for spaces and spheres for each of the mech elements. When I run the DoesIntersect node, it gives only 1 true value, though there are many intersecting. Could anyone help?
Cheers.

[BimAmbit]

Looks like a lacing issue. Try cross product for DoesIntersect.

[sanjaya]

Thanks for the quick reply. I did try that as well actually but had no luck.

[BimAmbit]

You might want to post some samples to help others reproduce the problem. Calvary will come.

[Nick_Boyts]

Please be sure to have your node preview bubbles pinned when taking a screenshot. Otherwise we’re just guessing at what’s actually happening in your graph.

Also, this exact process has been discussed many times on the forum already. Please make sure you are searching for similar topics before you start a new thread. There are multiple comments to be made on where your process needs to be improved (list levels, bounding box inaccuracies, boolean comparisons) that have already been discussed in those other topics. It’s best to start there and then come back with any specific questions you may have.

[sanjaya]

Hi Nick,
Thanks for the reply. I have gone through some of those processes and got to this point. Sorry, I’m a newbie to Dynamo and trying to get to the bottom of this.

Cheers.

[sanjaya]

Here is the script that I have done.

I did use one of these Mech samples to run it. Unfortunately, I can’t upload here as the file size is too big.

https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-61EF2F22-3A1F-4317-B925-1E85F138BE88

Space Intersecting elements.dyn (41.8 KB)

[BimAmbit]

I’ve run it with rvt 25 mep sample project, your graph yields a ton of true. A couple of things worth noting:

• bounding box is a rough representation of element geometry, you might want to use the original geometry of elements instead.
• “true” is a string literal, it’s text. true is boolean, you want to index stuff with the right thing.

I don’t find any major issues within your graph. Are you sure even after cross product, there’s only one single true?

[sovitek]

Hi @sanjaya all @BimAmbit say, dont use boundingboxes for your spaces these are always xy aligned…try ootb is.in.space node or as i like is in space from mepover as give the spaces without need a filter bool…you probably need translate your points in -z so you are sure they hit the spaces

[sanjaya]

I have tried both, but still I’m getting the same. Maybe I’m taking the spaces from the wrong node?

[sovitek]

try with element.solids here

PS and use cross product on your does it intersect node

[sanjaya]

Cheers for the reply.

The problem is that not all points are located within the space. such as fire dampers in the wall. I’m trying to get the intersecting space name for the fire dampers as well. That’s the reason I have created shares, so it will clash with the space and will give the intersecting space.

Thanks again…

[sovitek]

yes but should that firedamper belong to one space or 2 spaces ? anyway then we need translate the location point so it hit or as i think you already do use a oversized sphere so it probably will hit …

[sanjaya]

Yeah, I agree, fire dampers are in two spaces. Could this give an error if the sphere intersects more than 1 space?

[jacob.small]

@sovitek

think you already do use a oversized sphere

Location point would be faster as you don’t need to convert any geometry as you can query the room via the get room at point method. Just move the point in the facing direction of the family the same dimension used for the sphere. Bonus points if you try the center point first and then do the shifting of that returns null. Double bonus points if you use the room location point first, the location point of the instance second, and the offsets third as this can be used to account for the ‘above the ceiling’ stuff.

If both rooms are desired use both the + and - offsets.

As far as “could this give an error?”, well that depends. The logic above would find one (equipment’s center point is in the room) or two (dampener with + and - offset) rooms - but what are you planning to do once you find those? Setting a parameter value? Something else?

[sovitek]

here is a fast example…i use mepover in space here, you could use connector location point as well and tranlate them

[sanjaya]

@sovitek Cheers, Soren.

I have tried that, and it did work partially. I have 688 items, and I’m sure there are more than two in the spaces. However, it shows only 2 items. Thanks a lot for your help mate.

[sovitek]

Hi @sanjaya i guess not all elements have to be translated that way,only component in wall…try filter them out…try run it first lets say on 5 spaces …and see if it could work…and if then scale it up…if you have a small sample rvt you could share we could take a look…