Configuring the Creo View Interference Engine > Working with the Creo View Interference Engine > Interference Detection Input
  
Interference Detection Input
Use command line syntax to define items to include and exclude from a query.
Inclusions
After you define the test type, define 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 tags can contain a predefined child, as well as an optional soft tag with minAllowableClearance attribute.
Inclusion tags can contain multiple groupref or partref that are treated as a single group.
* 
If clashes occur for these inputs with multiple references, Creo View does not determine a top-level item.
To treat multiple items as a group when a Creo View group does not exist, you can use multiple partref in the inclusion instead of a single groupref:
<inclusion selfIntersect="false" id="id1">
<partref name="cam_gear"
allinstances="false" pvcidpath="/@@PV-AUTO-ID@@000/@@PV-AUTO-ID@@007"/>
<partref name="cam_gear2"
allinstances="false" pvcidpath="/@@PV-AUTO-ID@@000/@@PV-AUTO-ID@@008"/>
</inclusion>
* 
All item ids must be in the inclusion section.
The order of item ids is unimportant, meaning (id0, id1, c1) is the same as (id1, id0, c1).
An item pair shouldn’t appear more than once.
For 2 sets of inputs, item1 and item2 must be in different sets.
Clearance
You can set clearance values that are global, per input, or per input pair. These clearance values are hierarchical.
If two clearances of the same hierarchy are specified, the larger of the two values is applied.
When defining clearance, the most specific clearance is applied automatically.
If no specific clearance value is found, the minAllowableClearance value as defined per PVC file in the global clearance definition is applied.
<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>
After the <inclusions> section, you can add Per Input Pair clearance inside <clashDefinition>:
<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>
If there are multiple group pairs with Pair Clearance:
Use the maximum clearance value between all group pairs.
Use Per Input Pair clearance and ignore other clearance types.
Exclusions
You can exclude instances of specific items 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>
Group Pair — A pair of groups. To define pairs of groups, use this argument:
<exclusion>
<grouppair>
<grouprefname=”Small”>
<grouprefname=”Soft”>
</grouppair>
</exclusion>
Parts Pair – An exact pair of parts as defined by idpath. You can add excluded pairs to existing results and recalculate them.
* 
Inclusions are mandatory. A query must contain at least one <inclusion> definition. Inclusions contain an ID created by the XML.
Exclusions are optional and can be omitted if there are no items to exclude. Exclusions do not have an ID.