Examples: Interference Detection Reports
When the query is complete, a report file is generated. The report contains the input and definition parameters (in the <dataset> section) followed by a <report> section.
The default report file that is generated defines all item positions in absolute space if <reportDefinition> is not included in the input file.
Along with reporting the pairs of items that fail the test criteria, you can configure the report to include instance-specific properties. You can use these to trace back to identify the parts in an EPM system and so forth.
Example: How to Include the epmdoc_objectid Property (Supplied by Windchill) in the Report
The epmdoc_objectid property is supplied by Windchill.
Example: How to Include One or More <clash> Elements That Define Each Pair of Items That Have Made the Query Fail
The item ROTOR hard intersects with BAIL_WIRE. Because this example part does not include any analytical geometry (it is tessellated only) the results are tagged with the attribute approximated= “true” indicating that the VOLUME and PENETRATION results are approximate.
<report timestamp="20110427T134220">
<clashes>
<clash id="1">
<interferences>
<calculated type="VOLUME" value="2.366565583E-015"/>
<interference timestamp="20110427T134220"
type="hard" approximated="true">
</interference>
</interferences>
<clashItem1 name="ROTOR"
pvcidpath="…"/>
<clashItem2 name="BAIL_WIRE"
pvcidpath="…"/>
<intersections>
<intersection xmin="-7.65725076E-002" xmax="-6.43505156E-002"
ymin="-5.30253351E-002" ymax="-4.86363098E-002"
zmin="1.40132848E-003" zmax="2.19742227E-002">
</intersection>
</intersections>
</clash>
And so on.
The <interference> element defines what type of query failed. Here, it istype= “hard” along with specific values that were calculated. The two instances that failed are clashItem1 and clashItem2. The <intersections> element provides spatial information about the problem. The default is a globally-positioned bounding box (extents specified by xmin…zmax), and other information can be included inside the <intersection> element.
Example: A Simple All-structure Query
The <predefined> element can specify one of a number of predefined queries. Name= “all” specifies an all-structure query. If you include this in the XML file, complete with all the other elements, you can create an input file like this one:
You can run this (see all-structure.xml in the example data) using this clash script:
% pvsclashbatch all-structure.xml
When the script is complete, the interference detection tool generates an output file that is derived from the name of the input file. In this example, the file all-structure.pvc is generated.