Geometric Transformation of Objects in Enterprise Engineering Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise engineering systems face memory constraints when performing geometric transformations on large numbers of objects, as the main memory is insufficient to store all data structures simultaneously, leading to incomplete transformations and potential database inconsistencies.
Innovation Solution
The method involves dividing the objects into ordered partitions, processing them in sequential order, and performing geometric transformations in two passes: first, disconnecting external relationships and recalculating functional dependencies, and second, applying the geometric transformations while maintaining internal relationships intact, allowing for efficient memory usage and consistent database state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If all objects are loaded into main memory simultaneously for geometric transformation, then transformation completeness is improved, but memory availability deteriorates
Solution Approach 1:
The patent divides the set of objects into multiple partitions that can be processed sequentially. Each partition is loaded into main memory individually, transformed, and then committed to the database before the next partition is processed. This segmentation allows complete transformation of all objects while using limited memory resources at any given time.
Solution Approach 2:
The patent performs preliminary actions by disconnecting external relationships and recalculating functional dependencies before the actual geometric transformation. This preparatory work is done while objects are loaded in partitions, ensuring that when transformation occurs, all necessary computational groundwork is already in place, enabling complete transformation without requiring all objects to be in memory simultaneously.
2Quantity of substance
If objects are processed in sequential partitions, then memory usage is reduced, but transformation time increases
Solution Approach 1:
The patent maintains continuity of useful action by processing partitions sequentially without idle time. While one partition is being transformed, the system prepares the next partition by loading it into memory. This continuous processing minimizes the total transformation time despite the sequential nature of partition processing.
Solution Approach 2:
The patent performs preliminary actions such as disconnecting external relationships and recalculating functional dependencies before each partition transformation. This preparation work is done in advance while the system is actively processing, reducing idle time during the actual transformation phase and optimizing the overall transformation time.
3Reliability
If external relationships are disconnected before transformation, then database consistency is improved, but relationship integrity deteriorates
Solution Approach 1:
The patent performs preliminary actions by disconnecting external relationships and recalculating functional dependencies before geometric transformation. This ensures that objects can be transformed independently without violating database consistency. After transformation, relationships are re-established, maintaining both consistency and integrity.
Solution Approach 2:
The patent segments the transformation process into distinct phases: disconnection of external relationships, transformation of individual partitions, and re-establishment of relationships. This segmentation allows database consistency to be maintained during transformation while preserving relationship integrity through systematic reconnection after transformation completes.
4Manufacturing precision
If two-pass transformation is performed, then transformation accuracy is improved, but processing complexity increases
Solution Approach 1:
The patent segments the transformation process into two distinct passes: first pass for disconnecting external relationships and recalculating functional dependencies, and second pass for applying geometric transformations. This segmentation improves accuracy by ensuring all preparatory work is completed before transformation, while the modular structure keeps processing complexity manageable.
Solution Approach 2:
The first pass performs all necessary preliminary actions (disconnecting relationships, recalculating dependencies) before the second pass performs the actual transformation. This separation ensures transformation accuracy by guaranteeing that all computational prerequisites are met, while the systematic organization of the two passes keeps the increased processing complexity structured and manageable.
Data Source
AI summary
A large number of objects, such as objects representing beams and columns in an object-oriented enterprise engineering system, may be geometrically transformed in a model database by dividing the objects according to criteria into a number of ordered partitions and transforming the objects in each partition as an atomic operation. The number of objects that may be transformed is not constrained by the amount of memory available in the system. Objects that are to be transformed are organized into the ordered partitions, and the partitions are transformed in sequential order, such that all predecessors of a given object are transformed before, or in the same operation as, the given object. If a large transformation operation abnormally terminates before all the small transformation operations have been completed, the model database is, nevertheless, left in a consistent state. The transformation operation may be resumed from the point of interruption.