Configuring the Creo View Interference Engine > Working with the Creo View Interference Engine > Interference Detection Input
  
Interference Detection Input
Command line syntax can define which items to include and to exclude from a query.
Inclusions
After the definition of the test type, define the items to include in the query.
<clashDefinition>
<clashParams> … </clashParams>
<inclusions>… one or more items can be specified here </inclusions>
For standard mode each inclusion item is in its own tag.
<inclusions>
<inclusion selfIntersect="false" id="id3" >
<soft minAllowableClearance=".05"/>
<groupref name="HotParts"/>
</inclusion>
<inclusion selfIntersect="false" id="id4">
<groupref name="ColdParts"/>
</inclusion>
<inclusion selfIntersect="false" id="id5" >
<soft minAllowableClearance=".03"/>
<groupref name="WarmParts" />
</inclusion>
</inclusions>
* 
Inclusion content contains groupref, partref, or predefined
Optional soft tag with minAllowableClearance attribute
You can add Per Input Pair clearance inside clashDefinition after inclusions section.
<perPairClearances>
<perPairClearance item1=”id4” item2=”id3” minAllowableClearance =”1.1” />
<perPairClearance item1=”id4” item2=”id5” minAllowableClearance =”0.4” />
<perPairClearance item1=”id3” item2=”id3” minAllowableClearance =”0.8” />
</perPairClearances>
* 
All item ids must exist in the inclusion section.
Order of item ids is not important, (id0, id1, c1) is same as (id1, id0, c1)
The same item pair shouldn’t appear more than once
Between 2 sets of inputs, the item1 and item2 must be in different sets
Clearance
You can set clearance by global, per input, or per input pair. These clearance types are hierarchical. When determining the clearance to use, the most specific clearance is applied. If two clearances of the same hierarchy are specified, the larger of the two values is used.
The global clearance definition currently has a minAllowableClearance value, defined per PVC file. This is used if no specific clearance value is found.
<clashParams mode="QUICK">
<hard maxAllowablePenetration="0" active="true"/>
<soft minAllowableClearance="0.3" active="true"/>
<touch tolerance="0" active="true"/>
</clashParams>
To define clearance for pairs of groups, use the perPairClearances tag.
<perPairClearances>
<perPairClearanceitem1=”id4” item2=”id3” minAllowableClearance=”1.1” />
</perPairClearances
If, for example, you need to calculate the required clearance between P1 and P2, where P1 belongs to G1 and P2 belongs to G2, and "Per Input Pair" clearance is defined between G1 and G2, then use the clearance between G1 and G2 as follows:
If there are multiple pairs of G1 and G2 with pair clearance, then use the maximum clearance value between all group pairs that define clearance.
Use "Per Input Pair" clearance and ignore other clearance types.
Exclusions
Specific instances of specific items can be excluded from the query.
Exclude Group — A set of groups that does not send any potential pairs to the clash engine.
<exclusions>… one or more items can be specified here </exclusions>
<clashDefinition>
Parts Pair – Defines a pair of parts by idpath to exclude from the clash engine, excludes only the exactly same pair. You can an add exclude pairs on existing results and recalculate.
Group Pair — Defines a group of pairs that are excluded if the group pair is excluded. To define exclusion of groups of pairs, use this argument:
<exclusion>
<grouppair
<grouprefname=”Small”>
<grouprefname=”Soft”>
<grouppair
</exclusion>
* 
<inclusions> is mandatory. A query must contain at least one <inclusion> definition.
<exclusions> is optional and can be omitted if there are no items to exclude.
Inclusions contain an ID that was created by the XML, whereas exclusions do not have an ID.