Logging - Intergraph Smart 3D - Administration & Configuration - Hexagon

Intergraph Smart 3D Interference Checking

Language
English
Product
Intergraph Smart 3D
Subproduct
Interference Checking
Search by Category
Administration & Configuration
Smart 3D Version
13

To enable logging of codeless IFC rules, create the following empty log files in the %TEMP% folder for each user login before you start the Server IFC and Local IFC:

  • ModelName.CodelessIFCRules.log - for general user Local IFC

  • ModelName.CodelessIFCRulesTesting.log - for the testing mode described in Rule Development and Testing

  • ModelName.CodelessIFCRules.ServerIFC.log - for Server IFC mode

The software populates the log files as it processes clashes.

The ModelName.CodelessIFCRules.ServerIFC.log grows because the software appends rules each time it processes clashes. Either turn off logging before you start the Server IFC, or monitor the file size and disk space. If you need to keep the log, archive the log file and then empty it periodically.

Track rules based on time limit

Clash modification scenario log entry examples

Object is processed

@2/3/2015 4:54:13 PM - ProcessObject ? [Piping Components] - 'Flange-0403'

No rule is evaluated

ProcessObject -> Yes

Any rule is evaluated

--> Satisfied - /CustomClashRules/IgnoreObjectsForClashChecking/ByObjectType[0]
--> <ByObjectType List="Piping Welds"/>
ProcessObject -> No

A clash is detected

@10/28/2014 12:44:10 AM - CreateInterference ? - [Slab] - 'Slab-0101' & [Member Part Linear] - 'MemberPart-0202'

No rule is evaluated

CreateInterference -> Yes

Any rule is evaluated

--> Satisfied - /CustomClashRules/IgnoreClashesBetweenObjects/ByObjectType[1]
--> <ByObjectType List1="Slab" List2="Member Part *"/>
CreateInterference -> No

The software also generates log entries for SetClashType and SetClashProperty rule evaluations.