Checking Base and Top Constraints with Autodesk Model Checker (+ Revit LookUpTool)

Checking Base and Top Constraints with Autodesk Model Checker (+ Revit LookUpTool)

umberto_carenzo
Explorer Explorer
578 Views
3 Replies
Message 1 of 4

Checking Base and Top Constraints with Autodesk Model Checker (+ Revit LookUpTool)

umberto_carenzo
Explorer
Explorer

Good evening. I'm trying to implement a check for my business inside Autodesk Model Checker. I always used the traditional operators and criterias in it, so i have a little problem with the implementation of a parameter (i don't know if they are called internal parameters).

Anyway, i would like to check the Base and Top Constraint of a Wall, so in this case for the Base Constraint i normally use the Criteria "Level = Name", for the Top Constraint i discovered, via Revit LookUp Tool, that the parameter i can reach inside Autodesk Model Checker that is associated to it is WALL_HEIGHT_TYPE. The problem is that by adding this row inside my rule the checking doesn't work. Anyone knows if i'm doing something wrong using this "extra" parameters?

 

Thanks. 

123.PNG

456.PNG

0 Likes
579 Views
3 Replies
Replies (3)
Message 2 of 4

vitorbortoncello
Advisor
Advisor

For the Top Constraint try using the parameter `Top Constraint` directly instead of `WALL_HEIGHT_TYPE`, as that might not map correctly in Autodesk Model Checker.

A resposta te ajudou? Não esqueça de curtir e aceitar como solução!


Vitor Bortoncello | Arquiteto | BIM Manager


dAutodesk Certified Professional

0 Likes
Message 3 of 4

JasonKunkel
Collaborator
Collaborator

This just showed up via a search, hope the late reply might help the original poster.

 

Your approach using the built in parameter name "WALL_HEIGHT_TYPE" is the right instinct. 

 

Unfortunately, the parameter stores the data type Element ID (see StorageType in Revit Lookup). So the text you see in the Revit UI is not how the data is being stored "behind the scenes."

 

Checks in the Model Checker that refer to other elements or arrays of data can confuse the Model Checker. I have seen some success using the "Contains" Condition in the filter and typing in the actual Element ID for the value. Apologies that you might already be using Contains, but it looks like the value is the name of the level and not the Element ID.

 

So in the screenshot I included, I would filter for PARAMETER "WALL_HEIGHT_TYPE" CONDITION "CONTAINS" VALUE "9946". I have not tested this, but this would be the first thing I would try out.

 

2024-09-06_09-36-23.jpg


Jason Kunkel
Senior Practice Manager, Architecture and Engineering
CADD Microsystems Blog
RVIT Blog | Twitter | LinkedIn
0 Likes
Message 4 of 4

umberto_carenzo
Explorer
Explorer

Thanks for the reply. Unfortunately i tried as told, but it seems the Checker doesn't seems to store the data when using the Condition Contains + the actual Element ID. I don't know if you already tested this approach, or if you have any other idea or workaround to develop this check. Other than that, the main problem is that we are using a private BIM Standard of modeling that we developed, so the main concept in here is trying to automatize the following check: "The Base Constraint of Wall should be a level that follows a certain pattern of name (and this is possible, using "Level" + "Matches RegEx") and the Top Constraint should be a level that follows a certain pattern of name".  So, even if there is a workaround to get the value of the Top Constraint it should not be an exact value, but it should be a general expression of a RegEx, as for the Base Constraint.

 

Thanks in advance!

0 Likes