Classification of parameters in REVIT 1
0 Comments/in Sin categoría/by Jose MoraCLASSIFICATION OF PARAMETERS IN REVIT 1.
To understand the functioning of Revit, the first thing we have to consider is how it works?. Revit creates elements with a structure and characteristics that you are given a series of parameters. But how are these elements classified? We have different types of parameters? What are they like? How does it work?… All these questions that we can ask when we begin to delve into the performance is what leads to this introduction in that scene.
The first thing we need to know is that Revit works with families and are these which classified these elements. Depending on the type of family that is, the element will behave differently and have different parameters. There are three major groups of families: families of system, chargeable families and families modelled on-site (on-site component).
Depending on the type of family to which belong the element will have a different behaviour of these parameters. Since not with all the parameters we can work the same way and take that information in the same way. Then, what types of parameters are?.
The first classification that we would have to do would be distinguishing between type parameters and parameters of copy.
- Type parameters will affect all the elements belonging to the same type, within the same family. To differentiate them quickly they are those that we would find ourselves within the tab edit type.
- Parameters of exemplary, on the other hand, will only affect an element in particular, that it will be that have active and will not affect him the rest of elements of the same family or the same type.
Already differentiated type and specimen parameters, the next step would be to differentiate, depending on the family, that is, to that large group belonged. So now differentiate between the parameters of the families of system parameters of chargeable families and in situ.
Within the families of system we can find:
- Project parameters. They are parameters that can be added to all elements of a family. We can create our own project settings. They can vary depending on the project template that we use.
- System parameters. They are the parameters that Revit is configured by default. These parameters will always be the same in all projects and not depend on the project template that we use.
Chargeable families, can resemble them to families, since the creation of the same and its parameters will behave in a similar way, but are not going to be able to create the same types of families. For these types of families (chargeable and on-site) we can find the following parameters
- Parameters of family. These in turn could sort it: in those created by the user and that Revit has by default (in dependence on the type of family and the template family with which we begin the family in the case of the chargeable).
- Shared parameters. They are likely to be charged in other projects and be recorded parameters.
With this first introduction, we begin to situate ourselves in the functioning of Revit. But is there more?. Yes, but we'll see that later.
Juan Carlos Romero Avila
+ 34 954 32 38 85 info@mv-bim.com
Avda. Cardenal Bueno Monreal 56, 6ª planta.
41012, Sevilla
+ 34 910 86 74 72 info@mv-bim.com
Business Plaza. Plaza de José Moreno Villa, 2 Esc. Dcha 1º C.
28008, Madrid
Privacy Overview
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
didomi_token | never | This cookie is set by the provider Didomi. This cookie contains consent information for custom purposes and vendors along with the Didomi-specific information. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
pll_language | 1 year | The pll _language cookie is used by Polylang to remember the language selected by the user when returning to the website, and also to get the language information when not available in another way. |
Cookie | Duration | Description |
---|---|---|
AMCVS_9854C13E58403FEB0A495D53AdobeOrg | session | This cookie, set by Adobe Marketing Cloud, stores a unique ID to identify a unique visitor. |
AMCV_9854C13E58403FEB0A495D53AdobeOrg | 2 years | This cookie, set by Adobe Marketing Cloud, stores a unique ID to identify a unique visitor. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
demdex | 5 months 27 days | The demdex cookie, set under the domain demdex.net, is used by Adobe Audience Manager to help identify a unique visitor across domains. |
s_ecid | 2 years | Adobe installs this cookie to allow persistent ID tracking in the 1st party state and is used as a reference ID if the AMCV cookie has expired. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_137263943_1 | 1 minute | Set by Google to distinguish users. |
_ga_1YEHHVHKN2 | 2 years | This cookie is installed by Google Analytics. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
dpm | 5 months 27 days | The dpm cookie, set under the Demdex domain, assigns a unique ID to each visiting user, hence allowing third-party advertisers to target these users with relevant ads. |
everest_g_v2 | 1 year | The cookie is set under the everesttech.net domain to map clicks to other events on the client's website. |
everest_session_v2 | session | This cookie, set by Everesttech, is used for targeted ads and to document efficacy of each individual ad. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
ev_did | 4 years | No description available. |
ev_sid | 4 years | No description available. |
session | never | No description available. |
___iat_gid | 1 year | No description available. |
___iat_ses | 30 minutes | No description available. |
___iat_vis | 5 months 27 days | No description available. |
Leave a Reply
Want to join the discussion?Feel free to contribute!