Clash test settings Follow
This article provides descriptions of all clash test settings.
- Clash test name
- Selection
- Ignore clashes
- Clashing type
- Grouping
- Location tags
- View & screenshot
- Issue automation
- Access rights
- Labels
- Level model
- Grid models
See also:
Clash test name
A name that is displayed in the list of clash tests. Duplicate names are allowed.
The recommended name format is "A vs B", where A and B describe the selections that are checked for clashes.
Selection
A clash test defines two sets of objects that are tested for clashing against each other. Each object in selection A is tested for clashing with each object in selection B.
The selections are generated from search sets during clash detection.
Option | Description |
Search sets A | The search sets that generate selection A. |
Search sets B | The search sets that generate selection B. |
If you have many search sets, you can search by parts of their names. You can use the following wildcards:
- * any number of characters
- ? any character
Ignore clashes
You can specify conditions for ignoring clashes.
Simple conditions for ignoring clashes
Option | Description |
Ignore duplicates | If a clashing object includes a part of a mesh that is fully identical to a part of a mesh in the other clashing object, the clash is ignored. |
Ignore if both objects are in the same model | If clashing objects belong to the same Revizto model, the clash is ignored. |
Ignore room geometry | If a clashing object is a room, the clash is ignored. |
Ignore area geometry | If a clashing object is an area, the clash is ignored. |
Ignore zone geometry |
If a clashing object is a zone, the clash is ignored. |
Ignore space geometry | If a clashing object is a space, the clash is ignored. |
Advanced conditions for ignoring clashes
Most of the conditions are based on search sets. If you have many search sets, you can search by parts of their names. You can use the following wildcards:
- * any number of characters
- ? any character
Option | Description |
Ignore objects that are in the search sets | If an object belongs to any of the specified search sets, clashes with that object are ignored. |
Ignore objects A that are in the search sets | If an object from selection A belongs to any of the specified search sets, clashes with that object are ignored. |
Ignore objects B that are in the search sets | If an object from selection B belongs to any of the specified search sets, clashes with that object are ignored. |
Both objects have the same property value |
If clashing objects have the same value of a specific property, the clash is ignored. You can add any number of conditions of this type. To add a condition:
To remove a condition:
|
Both objects are in the same search set |
If both of the clashing objects belong to the specified search set, the clash is ignored. You can add any number of conditions of this type. To add a condition:
To remove a condition:
|
Object A and object B are in specifiec different search sets |
If an object from selection A belongs to search set A and an object from selection B belongs to search set B, clashes with those objects are ignored. You can add any number of conditions of this type. To add a condition:
To remove a condition:
|
Clashing type
This section contains the settings of the clash detection algorithm.
Option | Description |
Clashing type |
The rule that defines what is treated as a clash.
|
Choose what to clash |
The type of objects that are subject to clash detection, one of the following:
|
Ignore clashes within the same element |
If clashing geometries belong to the same element, the clash is ignored. This option is available only for clash detection between geometries. |
Grouping
This section contains the settings for automatic clash grouping.
Clash grouping conditions
Grouping conditions define how your clashes are grouped. By finding optimal conditions, you can greatly reduce the time required for manual clash analysis and eventually fully automate the creation of clash issues.
Usually, you will have between 1 and 4 grouping conditions. For example, if you choose "Level" and "Zone" conditions, each group will contain clashes from the same level and the same zone. The group "Ground Zone A" will contain clashes from level "Ground" and zone "Zone A".
Conditions are applied in the listed order, from top to bottom. To change the order, drag them by the icon.
The following condition types are available:
- Selection A/B
- Level
- Grid intersection
- Room
- Area
- Zone
- Space
- Proximity
- Chained proximity
- Property condition
- Group all clashes together in one group
Selection A/B
The clash grouping is based on physical objects. All clashes that include the same object from selection A or from selection B go to a single group.
For example, imagine that selection A includes pipes. If a specific pipe crosses several walls, grouping by selection A combines all these clashes together. The name of that pipe object will be included in the group name.
Option | Description |
Choose item to group by |
The physical object type (element or geometry) and clashing selection.
|
Level
The clash grouping is based on level. Clashes that don’t belong to any level go to the "No level" group.
To learn how to configure levels, see Level model.
Grid intersection
The clash grouping is based on grid intersections. Clashes that don’t have grid intersections nearby go to the "No grid" group.
To learn how to configure grids, see Grid models.
Room
The clash grouping is based on room. Clashes that don’t belong to any room go to the "No room" group.
Area
The clash grouping is based on area. Clashes that don’t belong to any area go to the "No area" group.
Zone
The clash grouping is based on zone. Clashes that don’t belong to any zone go to the "No zone" group.
Space
The clash grouping is based on space. Clashes that don’t belong to any space go to "No space" groups.
Proximity
Clashes go to the same group if they form a cluster where the distance between any two clash points does not exceed the limit.
Option | Description |
Regular/Chained | "Chained" switches the grouping condition to Chained proximity. |
Distance |
Clashes are grouped if the distance between any two clash points does not exceed this value. Some clashes that are close to each other might go to different clusters, as shown in the figure. |
Chained proximity
Clashes go to the same group if they form a chain where the distance between adjacent clash points does not exceed the limit. Chains can include multiple branches.
Option | Description |
Chained/Regular | "Regular" switches the grouping condition to Proximity. |
Chaining distance |
Clashes are grouped if the distance between adjacent clash points does not exceed this value. |
Max chain size |
If a chain size exceeds this value, the chain is split into shorter ones. A chain size is the distance between the two opposite corners of the smallest box that surrounds all clash points. |
Property condition
The clash grouping is based on a property of an element or geometry. All elements or geometries that have the same property value go to the same group.
Option | Description |
Select category | A property category. |
Select property | A property name. |
Search for property in |
The object type (element or geometry) and clashing selection.
|
Group all clashes together in one group
All clashes are added to a single group. If you select this option, do not add other grouping criteria.
Clash group name
Clash group names are based on the values of grouping parameters.
Words in braces {} are placeholders that will be replaced with parameter values. For example, {Room} will be replaced by a room name.
You can add custom text to the names. For example, "{Level} - {Room}" provides group names that include a level name and a room name separated with a hyphen.
- To add a placeholder, click its name above the Clash group name field.
- To remove a placeholder, put the cursor in the Clash group name field and delete the placeholder.
- To add custom text, type it in the Clash group name field outside of the placeholders.
Clash name
Clash names are based on the names of clashing elements and/or geometries.
Words in braces {} are placeholders that will be replaced with the names of elements or geometries. For example, {Element A} will be replaced by the name of the element A.
The default clash name is "{Element A} vs {Element B}". You can add geometry names to the clash name.
Examples:
- {Element A}: {Geometry A} vs {Element B}: {Geometry B}
- {Geometry A} vs {Geometry B}
Location tags
This section defines which location tags are added to clashes. By default, all location tags are added. However, if you want to slightly speed up clash detection in a large project, you might want to exclude the tags that are not important.
If your clash test includes a grouping by a location tag, the location tag is always added to clashes, regardless of the settings that you specify here.
Option | Description |
Calculate all location tags |
Add all available location tags to clashes. This includes level, room, space, zone, area, and grid intersections. For location tagging rules, see the descriptions of other checkboxes in this table. |
Level |
Tag clashes with levels. For additional options, see Level model. |
Room |
Tag clashes with rooms.
|
Space |
Tag clashes with spaces.
|
Revizto zone |
Tag clashes with zones.
|
Area |
Tag clashes with areas.
|
Grid intersections |
Tag clashes with grid intersections. Depending on the settings in the Grid models section, a clash is tagged with one or several grid intersections that are the closest to the clash point. |
View & screenshot
This section contains the clash viewpoint and clash issue screenshot settings.
Clash color settings
This section contains the settings for the colors of clashing objects.
Option | Description |
Clash colors |
The colors of clashing objects.
|
Default clash viewpoint settings
This section contains the default clash viewpoint settings.
Option | Description |
Default zoom factor | The default distance between the clash and the camera. You can override it for individual clashes by editing their viewpoints. |
Default section box size limit |
This parameter limits the size of the clash section box. For individual clashes, Revizto builds the smallest section box that includes both clashing objects. If the box width, height, or depth is more than twice this value, the box is cut to fit the limit. For clash groups, Revizto builds the smallest section box that surrounds all section boxes of individual clashes. If the Box height is defined by neighboring levels checkbox is selected, the box height will be adjusted AFTER the limit is applied. |
Box height is defined by neighboring levels | If you select this option, the top and bottom faces of the viewpoint section box are aligned with the neighboring levels. |
Issue screenshot settings
This section contains the settings that affect the clash issue screenshots. The screenshots are generated during the clash detection and during the sync with the issue tracker.
Option | Description |
Appearance |
The appearance that is applied to the 3D model when a clash issue screenshot is taken.
|
Clash Colors |
This parameter defines how clashes are highlighted.
|
Isolation |
This parameter defines whether clashes are isolated.
|
Transparency |
The transparency of clashing objects.
This works best when the bigger of two clashing objects is transparent. For example, if selection A contains pipes and selection B contains walls, we recommend that you make selection B transparent. |
Apply section box |
Defines whether the section box from the clash viewpoint is applied to the 3D model when the screenshot of that clash is taken. If you clear this checkbox, no section boxes are applied. We recommend that you select this checkbox for faster screenshot generation. |
Show grids |
Defines whether clash test grids are visible on clash issue screenshots. To learn how to configure clash test grids, see Grid models. |
Issue sync settings
This section contains the settings that define how clash issue screenshots and clash viewpoints are updated during the clash detection.
Option | Description |
Update screenshots |
This parameter defines which issue screenshots are updated during the clash detection.
Keep in mind that screenshot generation takes time. "None" is the fastest option, while "All" is the slowest one. |
Update viewpoint |
This parameter defines which issue viewpoints are updated during the clash detection.
|
Issue automation
This section contains the settings that apply to the generation of clash issues.
These settings only affect new issues that will be generated from the clash test. Changing these settings does not affect any existing issues.
General issue automation settings
This section contains the settings that have effect with both simple and advanced issue automation.
Option | Description |
Sync clash groups with the following statuses |
This parameter defines whether clash groups that have the Not reviewed status are synced with the issue tracker.
|
Add clash group number to the issue name | This parameter defines whether the clash group number (the value in the # column) is added to the issue name. |
Simple issue automation
Simple issue automation is a type of issue automation where a single rule defines a template for all issues created from a clash test.
We recommend that you configure simple issue automation for your first clash tests. When you become familiar with simple issue automation, you can switch to advanced issue automation, which is much more flexible.
Option | Description |
Stamp |
The stamp template to apply on issue generation. You can override the stamp template priority, assignee, and deadline by setting Priority, Deadline, and Assignee in this dialog. The watchers and tags specified in the stamp template are always added to the issues. You can specify additional watchers and tags in the Watchers and Tags fields in this dialog. To clear this field, open it for editing and click Reset. |
Priority |
The priority of new issues generated by the clash test. If this field is blank, the priority is inherited from the stamp template. When the priority is inherited, this field is marked with the following icon: . If a stamp template is not specified or has blank priority, the priority is set to None. To clear this field, open it for editing and select Reset. |
Deadline |
The deadline of new issues generated by the clash test. If this field is blank, the deadline is inherited from the stamp template. When the deadline is inherited, this field is marked with the following icon: . If a stamp template is not specified or has a blank deadline, the deadline is not set. Note that the weeks and months that you specify here are calendar weeks (starting on Monday) and calendar months. For example, if you specify a 1-week deadline here, the actual deadline is set to the next Monday. To clear this field, open it for editing, delete the value, and then click Apply. |
Assignee |
The assignee of new issues generated by the clash test. If this field is blank, the assignee is inherited from the stamp template. When the assignee is inherited, this field is marked with the following icon: . If a stamp template is not specified or has blank assignee, the assignee is set to the user that runs the sync with the issue tracker. To clear this field, open it for editing and select Reset. |
Watchers |
The watchers of new issues generated by the clash test. This includes the watchers inherited from the stamp template and the watchers that are explicitly added here. |
Tags |
The clash issue tags. This includes the tags inherited from the stamp template and the tags that are explicitly added here.
|
Switch to advanced automation. |
Switches the clash test to Advanced issue automation. This adds the option to add multiple issue generation rules. Each rule includes a condition that defines when the rule is applied. The issue generation rule that you configured in the simple automation mode becomes the default one. It is applied when none of the conditions are met. |
Advanced issue automation
Advanced issue automation allows you to configure multiple issue generation rules from a single clash test. Each rule includes the following:
- A condition that is checked for each clash group.
- An action that is performed when a clash group meets the condition, one of the following:
- Create an issue based on a specific template.
- Do not create an issue.
The order of rules matters. During the sync with the issue tracker, for each clash group, Revizto goes through the list of rules and executes the first one where the condition is met. If none of the conditions are met, Revizto executes the default rule, which is always the last one.
Adding issue automation rules
To add an issue automation rule:
-
In the Issue automation (Advanced) window, under CONDITIONAL VALUES, click Add condition.
This adds a placeholder for a conditional rule.
-
In the IF field, select a condition type.
If a condition includes "objects A" or "objects B", it is checked only for objects from selection A or selection B.
-
If you want to add a second part to the condition, at the right of the IF field, click and select a condition type.
You can join the condition parts with one of the following operators:
-
AND. The condition is met when both its parts are met.
-
OR. The condition is met when at least one of its parts is met.
To toggle between AND and OR, click the operator.
-
-
In the that match(es) the search sets field, click and select one or several shared search sets.
If you have many search sets, you can search by parts of their names. You can use the following wildcards:
- * any number of characters
- ? any character
-
In the THEN field, select whether you want to have an issue created.
If you select "Create issue", you can specify some of the issue fields. For descriptions of these fields, see Simple issue automation.
Ordering issue automation rules
The rules are applied from top to bottom. Revizto applies the first rule where the conditions are met and skips the rest of the rules.
To change the position of an issue automation rule:
-
In the Issue automation (Advanced) window, drag a rule by the icon in the upper-left corner of the condition.
Deleting issue automation rules
To delete an issue automation rule:
-
In the upper-right corner of the condition, click .
Access rights
This section contains the list of project members and their rights in the clash test. For more information, see Managing clash test access rights.
Labels
This section contains the clash test labels. You can use labels to filter clash tests.
- To add a label to a clash test, type the label name, select a checkbox next to it, and click Apply.
- To remove a label from a clash test, clear the checkbox next to it and click Apply.
- To remove all labels from a clash test, click Clear selected items, and then click Apply.
Level model
This section contains the settings for levels that are used as location tags in this clash test.
-
Use project levels. The clash test uses the levels defined in the project. To edit the levels, click Edit project levels.
When you edit project levels, your changes apply to the entire project.
-
Use custom levels. The clash test uses the levels defined here. You might want to use this option if your project includes several buildings, each with its own levels.
To edit the levels, click Edit custom levels and refer to the table below.
Option Description Model to use the levels from The model that provides the levels. When adding location tags to clashes The method of defining the clash level.
- Use the level of the clash. Tag clashes with the closest level under the clash point.
- Use the level above the clash. Tag clashes with the closest level above the clash point.
Grid models
This section contains the settings for grids that are used in location tags in this clash test.
-
Use project grids. The clash test uses the grids defined in the project. To edit the grids, click Edit project grids.
When you edit project grids, your changes apply to the entire project.
-
Use custom grids. The clash test uses the grids defined here.
To edit the grids, click Edit custom grids or Configure custom grids, and refer to the table below.
Option Description When adding location tags to issues or clashes The method of defining the closest grid intersections for the clash.
- Store the closest grid intersection. Tag clashes with the grid intersection that is the closest to the clash point.
- Store all grid intersections within __. Tag clashes with all grid intersections that are within the specified distance from the clash point.
Select the models to use the grids from The models that provide the grids.
Comments
0 comments
Article is closed for comments.