
--------------------------------------------
back_trace_TEST8
--------------------------------------------
Files To Be Analyzed:  from test_case_files_list_short.txt
1.  pdi_0-e5-242.stp			   [step file from R55J, published from Elysium (CATIA V5 source), with v5 UUIDs]
2.  pdi_0-e5-242_STEP_UUIDs_TEST8.qif	   [QIF Plan file, published from metrology planner after ingesting published STEP file]
					   [includes STEP v5 UUIDs defined as ExternalIDs in a <Product><Part><DefinitionExternal> table and 
					   attached to <DatumDefinition>s, <FeatureNominal>s, and CharacteristicNominal>s as appropriate]
3.  pdi_0-e5-242_Results_TEST_xIDs.qif     [QIF Results file, published from metrology Execution/Analysis system]
					   abbreviated Results file using only xIDs on CharacteristicItems
					   [attached to CharacteristicMeasurement>s for each of three <MeasurementResultsSet>s]

Consider: Rules_for_UUID_Relationship_Analyses_v8.txt

Goal: perform a backward trace from ALL characteristics in QIF Results via either direct UUID matching or via indirect ExternalEntityID referencing or via QIF Identifier matching or via QIF external IDs for the set of files provided; Identify an failed characteristics.  Consider a UUID trace or an ExternailEntityID trace or a QIF Identifier trace or a QIF External Identifier a success and consider a name-based trace as a failed trace.

Output: A web page table of tracing each UUID found with all associated STEP and/or QIF entities in the file set.  Publish the date of execution as a hard date in the html file

Output Results - back_trace_TEST8_20251216.html





