Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Autodesk Model Checker Configurator (advanced filter)

5 ANTWORTEN 5
GELÖST
Antworten
Nachricht 1 von 6
gautier_vasseur
1518 Aufrufe, 5 Antworten

Autodesk Model Checker Configurator (advanced filter)

Hello everybody,

 

I work on Revit Model Checker since few days and I begin to configurate advanced filters in the configurator.

However, I try to create 2 filters but i still don't know how to do it :

-the first one, to determinate if a starting view is selected

-the second, to determinate if an IFC configuration export is selected

For now, you'll find attached what I've done/tried (pic1 & pic2)

 

Beyond these 2 filters, I would like to undertand and know how to find and use API Types & API Parameters (pic3).

I have the intuition that this site can be very usefull, referencing all the Revit API, but I don't know a lot more : https://www.revitapidocs.com/2020.1/

 

Regards :leicht_lächelndes_Gesicht:


LinkedIn GIF

Beschriftungen (2)
5 ANTWORTEN 5
Nachricht 2 von 6
JasonKunkel
als Antwort auf: gautier_vasseur

I am not sure on your specific examples, yet, but I can offer some insight into the API Parameter and API Type.

 

In the Model Checker Configurator, API Parameter refers to Properties in the Revit API. The Model Checker cannot get every Property successfully, so you have to do a lot of testing. But, for example, the Property "Pinned" is something the Model Checker can check via an API Parameter filter. It's not a traditional Revit Parameter but it is a Property of the element. Like I said, not all Properties can be access via the API. Most that refer to other elements are not accessible. If you use the Lookup Tool (which I STRONGLY recommend if you are building advanced checks) these would be the Properties in bold that the Model Checker definitely has problems with. Again, you need to test a lot b/c sometimes it just won't work.

 

The API Type is digging into the Revit database directly. Again, referring to the Lookup Tool, if you "Snoop Database" that is a great place to start looking around. Again, some simply don't work, but you do get lucky. If you look at the Public Library of checks, the Best Practices check has "In-Place Families" which uses both an API Type and API Parameter to check Autodesk.Revit.DB.Family and IsInPlace. We don't use the API Type as often as API Parameter, but you can get things like shared parameter information or every placed instance using the API Type.

 

I would strongly recommend looking through all the checksets available in the Public Library for more examples.


Jason Kunkel
Senior Practice Manager, Architecture and Engineering
CADD Microsystems Blog
RVIT Blog | Twitter | LinkedIn
Nachricht 3 von 6
gautier_vasseur
als Antwort auf: gautier_vasseur

There is the exemple of the starting view test which I managed to create (attached).

Thanks to the LookUp plugin, I noticed the value of the "ViewId" parameter of the Starting View was -1 when no view was defined. Then, when this value is -1, my test is negativ :leicht_lächelndes_Gesicht:

Thanks for your recommanding me this plugin, it's very usefull but as you said it's clear that Model Checker is limited. A lot of API Type/parameters don't work and you can't compare 2 parameters.

 

Again today I'm don't know how to do a simple thing : Have all the Generic Model visible on a view.

When you call the OST_GenericModel category, it calls all the GenericModel in the project. There must be a visibility parameter that tells you if an object is on a view or not but I can't find it...


LinkedIn GIF

Nachricht 4 von 6
JasonKunkel
als Antwort auf: gautier_vasseur

That is a great check! I am glad you got it working.

 

Checks of elements in Views are definitely challenging because you actually need to check the View, not the Elements. In the API, the View is what tracks what elements are hidden and the Model Checker would need an extra layer to check the array of IDs that it stores. Maybe that helps get you some next steps? I would be curious if you can put something together.

 

Per your comment about comparing Parameters - the Model Checker CAN compare one "standard" Parameter to another in the same element. It cannot compare API Parameters if that's what you mean. If you are just comparing regular Parameters, look at the filter "Matches Parameter" and "Does Not Match Parameter" for a Parameter Criteria filter.


Jason Kunkel
Senior Practice Manager, Architecture and Engineering
CADD Microsystems Blog
RVIT Blog | Twitter | LinkedIn
Nachricht 5 von 6
gautier_vasseur
als Antwort auf: gautier_vasseur

I'm not sure to understand what you mean by "add an extra layer to check the array of IDs that it stores". Do you mean checking all the view parameters thanks to LookUp plugin ? Sorry my english is not perfect as you may see ahah

 

Oh yeah actually you can compare 2 normal parameters, I didn't know that, thanks for this tips. The translation of this condition was mistranslated in my language.


LinkedIn GIF

Nachricht 6 von 6
JasonKunkel
als Antwort auf: gautier_vasseur

Sorry for adding to the confusion. What I mean by "an extra layer" is that in the Revit API there are some Properties ad Methods that return multiple items. First off, the Model Checker does not work with Methods unless it is a Pre-Built check. The Properties (API Parameters) that return multiple items are also a problem for the Model Checker. I meant an "extra layer" of elements and objects. The Model Checker wants to only look "one layer" deep when checking element information.

 

I hope that helps and doesn't confuse things more.


Jason Kunkel
Senior Practice Manager, Architecture and Engineering
CADD Microsystems Blog
RVIT Blog | Twitter | LinkedIn

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report