XML Comparison - Intergraph Smart 3D - Reference Data - Hexagon

Intergraph Smart 3D Structural Manufacturing Reference Data

Language
English
Product
Intergraph Smart 3D
Subproduct
Structural Manufacturing
Search by Category
Reference Data
Smart 3D Version
13.1

Typically, you should generate a new output file for recomputed parts. For XML output, however, you can customize the configuration file so that the software compares a recomputed part to the original part and updates the data only if the comparison shows significant changes.

Add the COMPARE attribute to the configuration file and to the S3DPackageDefinition that created the output being compared. The COMPARE value should be the comparison schema used for the comparison. The COMPARE value is StructManufacturing\ManagedExport\
BaseSchemaForMFGPlate.xml in the example below.

<S3DPackageDefinition NAME="SMS_SCHEMA_PLATE" TYPE="S3DDocument" DATAFORMAT="CMfgPlateOutputCmd_DEFAULT" FOLDER="" DOCUMENT_PROCESS="Create" COMPARE="\StructManufacturing\ManagedExport\BaseSchemaForMFGPlate.xml">
<S3DOutput>
<Attachment>
<AttachmentType>S3D_DOCUMENT_TYPE</AttachmentType>
<AttachmentID>S3D_ATTACHMENT_ID</AttachmentID>
<Definition>CONST_S3D_ATTACH_SMS_PLATE</Definition>
<Path>S3D_DOCUMENT_PATH</Path>
<FileName>S3D_DOCUMENT_NAME</FileName>
1.0S3D_DOCUMENT_VERSION</Version>
</Attachment>
</S3DOutput>
</S3DPackageDefinition>

The XML comparison can be customized by modifying the specified schema or giving a different schema to use for the comparison. If the user has added new attributes to the XML output, these attributes can be added to the comparison schema to be included in the comparison.

You can customize the XML comparison by modifying the specified schema, entering a different schema, adding new attributes from the XML output to the schema used for comparison.

Example

In the example below, a new attribute (PART_SEQUENCE) is added to the SMS_PART_INFO node. A new entry for the attribute is added to the compare schema, and the software includes the new attribute when comparing different versions of the generated data.

<SMS_PART_INFO CHILDREN="no" INCLUDE_IDENTICAL="no" ERROR_MESSAGE="Error NODE1" ERROR_CODE="4">
<COMPARE_ATTRIBUTES>
<ATTRIBUTE NAME="PART_VERSION" TYPE="INTEGER" PROCESS="" TOLERANCE=".1" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="PART_BOARDSIDE_PROCESSED" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="PART_BOARDSIDE" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="PART_NAME" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="DEVELOPMENT_DIR_U" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="DEVELOPMENT_DIR_V" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="WEIGHT" TYPE="DOUBLE" PROCESS="" TOLERANCE=".001" ERROR_CODE="0" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="PART_TYPE" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="COMMON_PART_NAME" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="MATERIAL_TYPE" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="MATERIAL_GRADE" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="MEMBER_CATEGORY" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME="TOTAL_AREA" TYPE="DOUBLE" PROCESS="" TOLERANCE="0.1" ERROR_CODE="0" INCLUDE_IDENTICAL="no"/>
<ATTRIBUTE NAME=" PART_SEQUENCE" TYPE="STRING" PROCESS="" TOLERANCE="" ERROR_CODE="4" INCLUDE_IDENTICAL="no"/>
</COMPARE_ATTRIBUTES>
</SMS_PART_INFO>