Tidy command
Tidy command
How can tidy command help us in the modelling? How can we use it? Can we also use it to fix missing surfaces in the geometry?
Re: Tidy command
Hi,
The tidy commands were introduced to improve the quality of geometry in models imported from Revit (or SketchUp) via gbXML. It can be useful for models built in ModelIT but it is less likely you will get a poor quality model from using the ModelIT tools compared to a gbXML import which depends entirely on the source model/software export quality.
Quick description of some useful ModelIT key-ins then:
Tidy: "tidy"
scans the selected room, fills in all the gaps between disconnected edges, and then merges polygons in the same plane, with shared edges.
Note: this is called automatically for each room in turn when it is imported via the gbXML import process. Occasionally, a repeat application of this key-in can yield fruit on extremely fractured geometries.
Tidyunbound: "tidyunbound"
looks at a selected room, detects any surfaces with disconnected edges, and removes the ‘unbound’ surfaces because any disconnected surfaces cannot be part of a volumetrically bound shell.
Useful to tidy up some of the more fractured ‘rooms’ that can come from external geometry files.
Tidymirror: "tidymirror"
looks at the selected room, and detects surfaces which lie in the same plane, but face in opposite directions (are mirrors of each other). It clips them in relation to other polygons, and then deletes any remaining pairs of mirrored faces facing in opposing directions.
These forms of surfaces are usually present in gbXML where there are offshoot floating surfaces outside a room volume, and are effectively a mirror image of each other.
Tidysurfs: "tidysurfs"
calls “tidyunbound†and then “tidymirrorâ€.
Phil
The tidy commands were introduced to improve the quality of geometry in models imported from Revit (or SketchUp) via gbXML. It can be useful for models built in ModelIT but it is less likely you will get a poor quality model from using the ModelIT tools compared to a gbXML import which depends entirely on the source model/software export quality.
Quick description of some useful ModelIT key-ins then:
Tidy: "tidy"
scans the selected room, fills in all the gaps between disconnected edges, and then merges polygons in the same plane, with shared edges.
Note: this is called automatically for each room in turn when it is imported via the gbXML import process. Occasionally, a repeat application of this key-in can yield fruit on extremely fractured geometries.
Tidyunbound: "tidyunbound"
looks at a selected room, detects any surfaces with disconnected edges, and removes the ‘unbound’ surfaces because any disconnected surfaces cannot be part of a volumetrically bound shell.
Useful to tidy up some of the more fractured ‘rooms’ that can come from external geometry files.
Tidymirror: "tidymirror"
looks at the selected room, and detects surfaces which lie in the same plane, but face in opposite directions (are mirrors of each other). It clips them in relation to other polygons, and then deletes any remaining pairs of mirrored faces facing in opposing directions.
These forms of surfaces are usually present in gbXML where there are offshoot floating surfaces outside a room volume, and are effectively a mirror image of each other.
Tidysurfs: "tidysurfs"
calls “tidyunbound†and then “tidymirrorâ€.
Phil
IES Worldwide Technical Support