Multiple Independent Graphs for Component Organization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing hierarchical data structure used in computer graphics is unwieldy, error-prone, and time-consuming for managing and manipulating large numbers of components, forcing all workers to view and manipulate components in the same way, which reduces efficiency and can lead to errors due to changes in component locations and relationships.
Innovation Solution
The use of multiple independent graphs or hierarchies allows components to be organized and viewed according to arbitrary relationships, enabling software tools to specify and enforce functional relationships independently, and allowing for the progressive modification of relationships without disrupting the digital production pipeline.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single hierarchical data structure is used to organize all components, then the structure is simple to implement, but it becomes unwieldy and error-prone when managing large numbers of components
Solution Approach 1:
The patent divides the single hierarchical data structure into multiple independent graphs, each serving specific organizational purposes. Components can be members of multiple graphs simultaneously, allowing different views and relationships to be maintained separately without interfering with each other, thus resolving the unwieldiness of managing all components in one structure.
Solution Approach 2:
The patent introduces additional organizational dimensions by creating multiple graphs that represent different relationships and views of components. Instead of forcing all relationships into a single hierarchical dimension, components can be organized along multiple independent dimensional axes, each graph representing a different dimension of organization.
2Stability of the object's composition
If all workers must view and manipulate components in the same way according to the master hierarchical structure, then the data structure remains consistent, but productivity and efficiency are reduced
Solution Approach 1:
The patent segments the monolithic master hierarchical structure into multiple specialized graphs. Each graph can be optimized for specific workflows and views needed by different workers, allowing simultaneous access and manipulation without compromising overall data consistency. Workers can operate on relevant subsets of relationships without affecting the entire structure.
Solution Approach 2:
Different graphs can have different organizational qualities and characteristics tailored to specific needs. For example, one graph might be optimized for spatial relationships, another for temporal sequences, and another for dependency relationships. Each graph can be manipulated and viewed according to its specific quality requirements while maintaining consistency with the overall system.
3Ease of manufacture
If component relationships are specified by their location in the hierarchical structure, then the structure automatically defines relationships, but moving or renaming components changes their relationships unintentionally
Solution Approach 1:
The patent extracts the relationship specification from the positional location in the hierarchy and places it into explicit relationship attributes and membership definitions in multiple graphs. Relationships are no longer implicitly derived from position but are explicitly declared and maintained as separate data elements, allowing position changes without automatic relationship changes.
Solution Approach 2:
The patent creates copies of relationship information across multiple independent graphs rather than relying on a single hierarchical position. Each graph maintains its own copy of relevant relationships, so moving a component in one graph does not automatically change relationships in other graphs where the component's position remains stable.
4Quantity of substance
If thousands or millions of components are stored in the master hierarchical structure, then all components can be organized in one place, but creation, modification, manipulation, debugging, and processing become unwieldy and time-consuming
Solution Approach 1:
The patent segments the large set of components into multiple graphs, each containing a subset of relationships and components relevant to specific purposes. This allows workers to focus on smaller, manageable subsets of relationships within each graph rather than navigating through all components in a single massive hierarchy, significantly reducing the time and complexity of manipulation and debugging.
Data Source
AI summary
The components of a computer graphics scene can be organized using multiple independent graphs. Each component can include graph relationship attributes specifying its location in one or more graphs. Graph can be utilized for any purpose within the digital production pipeline. A component can include any number of graph relationship attributes. The number and type of graph relationship attributes can be different for each component. Software tools can access one or more graphs to determine structural or functional relationships between components. Software tools can enforce policies for a graph independent of other graphs. Software tools can optimize the components of a graph independent of other graphs. A graph relationship attribute of a component can include optional parameter data to specify properties of the relationship between two or more components. Layer data structures including opinions of value can specify graph relationships.