Simulator Object Registration in Circuit Design Tools
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current approaches for integrating simulators into circuit design tools are inefficient due to increased maintenance costs and delayed bug fixes, as they require rebuilding the design tool with each simulator update, involving multiple parties and complex compilation processes.
Innovation Solution
A method of linking simulators to a circuit design tool by establishing simulator objects in response to registration commands, which store property values referencing simulation interface procedures, allowing for customizable simulation flows without compiling the design tool, enabling independent updates and maintenance of simulators.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If simulators are integrated into circuit design tools through compilation-based linking, then simulation functionality is provided within the design tool, but maintenance costs increase and bug fixes are delayed due to required rebuilds
Solution Approach 1:
The system separates the circuit design tool from simulator components by using independent simulator objects that can be registered and unregistered without recompiling the design tool. This segmentation allows the simulator to be updated, maintained, or replaced independently from the core design tool, eliminating the need for rebuilds when simulator changes are made.
Solution Approach 2:
The patent introduces an intermediary registration mechanism that acts as a bridge between the simulator and the design tool. Through registration commands, simulator objects are dynamically linked to the design tool without requiring compilation. This intermediary layer enables loose coupling, allowing simulator updates to occur independently while maintaining integration functionality.
2Adaptability or versatility
If simulators are compiled together with the design tool, then integrated functionality is achieved, but updates to simulators require rebuilding the entire design tool
Solution Approach 1:
The system transitions from a static compiled integration to a dynamic registration-based integration. Simulator objects can be registered, unregistered, and updated at runtime without requiring the design tool to be rebuilt. This dynamic approach allows for flexible updates and changes to simulator components while maintaining integrated functionality.
Solution Approach 2:
The patent implements preliminary registration commands that establish simulator objects before they are needed for simulation. This allows simulator components to be pre-configured and registered with the design tool in advance, enabling quick updates and swaps without requiring compilation or rebuild processes when changes are needed.
3Reliability
If multiple parties are responsible for simulator and design tool operation, then specialized expertise is utilized, but coordination complexity increases and bug fixes are delayed
Solution Approach 1:
The registration command interface provides a universal mechanism that works across different simulator types and parties. The standard registration process allows any simulator provider to integrate their simulator with the design tool through a common interface, reducing coordination complexity while maintaining the ability for specialized parties to contribute their expertise.
Solution Approach 2:
The system enables self-service integration through automated registration commands. Simulator objects automatically register themselves with the design tool through standardized commands, reducing the need for manual coordination between multiple parties. This self-organizing mechanism simplifies the interaction between different responsible parties while maintaining specialized functionality.
Data Source
AI summary
Simulators are linked to a circuit design tool by establishing a plurality of simulator objects in response to a plurality of registration commands, respectively. Each registration command specifies a simulation interface application associated with one of the simulators, and the simulation interface application has procedures for initiating functions of the associated simulator. For each simulator, values of properties of the simulator are stored in the respective simulator object. The values of the properties include references to the procedures of the associated simulation interface application. An interface, which is responsive to input commands, accesses the values of the properties and executes the procedures referenced by the values of the properties to initiate the functions of the simulators.