CAD Conversion Acyclic Graph Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing CAD conversion techniques face challenges in addressing spatial ambiguities and preserving human-readable names and information relationships when converting from a file-based storage format to a relational database-based storage format, particularly due to multiple root models, cycles, and multiple attachment paths leading to element duplications and loss of information relationships.
Innovation Solution
The technique generates an acyclic model graph using a single project coordinate system, duplicates models as needed to break cycles, and preserves human-readable names and information relationships by creating categories and subcategories, ensuring a coherent representation and maintaining display status and symbology overrides in the relational database-based storage format.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing CAD conversion techniques are used to convert from file-based storage format to relational database-based storage format, then conversion between different CAD applications is enabled, but spatial ambiguities and information relationship losses occur due to multiple root models, cycles, and multiple attachment paths
Solution Approach 1:
The patent segments the model graph into multiple acyclic subgraphs, each corresponding to a specific graphical view. By breaking down the complex model graph with cycles and multiple root models into view-specific acyclic subgraphs, the conversion process can preserve information relationships while enabling interoperability between different CAD applications and versions.
2Adaptability or versatility
If existing CAD conversion techniques are used, then conversion between different CAD applications is enabled, but element duplications occur due to multiple attachment paths
Solution Approach 1:
The patent segments the model graph into multiple acyclic subgraphs, each corresponding to a specific graphical view. By breaking down the complex model graph with cycles and multiple root models into view-specific acyclic subgraphs, the conversion process can preserve information relationships while enabling interoperability between different CAD applications and versions.
Solution Approach 2:
The patent performs preliminary actions by identifying and resolving cycles and multiple attachment paths before the actual conversion process. The system pre-processes the model graph to establish a coherent representation that eliminates duplications, ensuring accurate element mapping during conversion to the relational database-based storage format.
3Productivity
If a direct conversion approach is used, then conversion speed is maintained, but coherence and accuracy of the CAD representation deteriorate due to spatial ambiguities
Solution Approach 1:
The patent performs preliminary actions by identifying and resolving cycles and multiple attachment paths before the actual conversion process. The system pre-processes the model graph to establish a coherent representation that eliminates duplications, ensuring accurate element mapping during conversion to the relational database-based storage format.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In one embodiment, techniques are provided for converting a CAD description maintained in a first storage format (e.g., a file-based storage format) of a source re-pository to a second storage format (e.g., a relational database-based storage format) of an output repository. The techniques may, generate a single, coherent representa-tion from spatially ambiguous "fragments" by generating an acyclic model graph for each graphical view, and then storing models of the acyclic model graph in the second storage format (e.g., the relational database-based storage format). The techniques may further produce a post-conversion CAD description that preserves human-readable names and information relationships related to levels by examining attach-ment specific copies of level structures (i.e. levels and attached levels) referenced from attachments, and generating from these categories and subcategories in the second storage format (e.g., the relational database-based storage format).