Abstract: A device may generate a graph of a set of elements included in a graphical user interface. An attribute of an element, of the set of elements, may be represented by a vertex of the graph. A layout relationship associated with the set of elements may be represented by an edge of the graph. The device may detect a change to the graphical user interface from a first display condition to a second display condition. The device may determine another vertex location for the vertex corresponding to another attribute for the element based on detecting the change from the first display condition to the second display condition and based on the graph of the set of elements. The device may provide, for display, the set of elements in the second display condition based on the other attribute for the element.

Abstract: A virtual driver interface and strategy are presented for interfacing a device driver with an application. Devices connected to a computing device and device drivers capable of communicating with the device are provided on the computing device. The virtual driver interface determines which of the device drivers to use to allow an application to interact with a device based on a strategy.

Abstract: Test configurations are generated based on information regarding hardware or software. A desired test configuration is selected. Test elements are automatically generated based on the desired test configuration, the test elements for testing at least one of the hardware or software. A plurality of test vectors is generated to test the hardware or software for the desired test configuration. The desired test configuration is converted to a script file. At least one of the hardware or software is automatically tested using the script file. Automatically testing the at least one of the hardware or the software includes using a first set of one or more test vectors from the plurality of test vectors to perform a plurality of test iterations of one or more of the actions of one or more generated test elements, and includes using at least a second set of one or more test vectors from the plurality of test vectors to determine the number of test iterations. A result of the testing is produced.

Abstract: In one embodiment, a test and measurement application executing on a computing device is interfaced with one or more external device coupled to the computing device. A device driver is selected for use with one of the external device from two or more available device drivers that are each compatible with the external device. The device driver is coupled to a virtual driver interface that provides the test and measurement application with a standardized interface to any of the two or more available device drivers. The test and measurement application communicates with the external device through the virtual driver interface.

Abstract: A viewer is disclosed for viewing a multi-dimensional data set. The viewer may be coupled to or included in a test environment and receive data generated in the test environment. The test environment may generate metric data from the multiple test cases of a UUT. The viewer may display the cumulative metric data generated from multiple test cases. The viewer may display the cumulative metric data in a fashion that the user can gain insight into the UUT's characteristics.

Abstract: Generating cumulative metric data for a test in a test environment includes: generating in the test environment a test for a simulation model of a system under test; generating in the test environment at least one test condition for the test, the at least one test condition determining a plurality of iterations of the simulation model; generating in the test environment at least one temporary test variable for the test; generating in the test environment at least one mapping between a metric setting for the simulation model and one of the temporary test variables; running in the test environment the test for the plurality of iterations, wherein metric data for the simulation model is generated for each mapping and for each iteration of the test; and accumulating in the test environment the generated metric data for each mapping and for each iteration of the test to obtain cumulative metric data for the simulation model.

Abstract: A test for testing at least one of hardware or software in a first environment is generated. A desired test configuration is selected based on information regarding respective hardware or software. Test elements are automatically generated based on the desired test configuration, the test elements adapted to test at least one of the hardware or software. At least one of the hardware or software is automatically tested using a subset of the test elements. A result of testing is produced.

Abstract: A viewer is disclosed for viewing a multi-dimensional data set. The viewer may be coupled to or included in a test environment and receive data generated in the test environment. The test environment may generate metric data from the multiple test cases of a UUT. The viewer may display the cumulative metric data generated from multiple test cases. The viewer may display the cumulative metric data in a fashion that the user can gain insight into the UUT's characteristics.

Abstract: Generating cumulative metric data for a test in a test environment includes: generating in the test environment a test for a simulation model of a system under test; generating in the test environment at least one test condition for the test, the at least one test condition determining a plurality of iterations of the simulation model; generating in the test environment at least one temporary test variable for the test; generating in the test environment at least one mapping between a metric setting for the simulation model and one of the temporary test variables; running in the test environment the test for the plurality of iterations, wherein metric data for the simulation model is generated for each mapping and for each iteration of the test; and accumulating in the test environment the generated metric data for each mapping and for each iteration of the test to obtain cumulative metric data for the simulation model.

Abstract: A system and method encapsulates selected functionality of a programming environment, defines an interface to the encapsulated functionality, and utilizes the encapsulated functionality from within an add-on toolbox to the programming environment through the interface. Objects may be constructed from the selected functionality of the programming environment. The functionality may be built-in or custom designed functionality. The objects are registered with the add-on test toolbox, and made available to a user of the add-on toolbox. The user may enter information into a user interface specifying selected functionality and its properties. An object manipulation engine receives the to information entered into the user interface, and uses it to issue calls through the interface to construct the objects and invoke one or more of the methods.

Abstract: A method for testing a system under test includes defining a test having a number of test elements where at least one of the test elements corresponds to a simulation model with a metric setting. A test vector is defined for the test, and it is used to determine a number of test iterations. The metric setting of the simulation model is mapped to a test variable, and when the test is run metric data is generated from the simulation model during each test iteration. The metric data generated for each test iteration is accumulated and displayed.

Abstract: A method of creating and using a hardware independent communication interface block for block diagram environments is disclosed. The communication interface block includes user-selectable parameters controlling how a system being modeled by a block diagram communicates with image and data acquisition devices and control instruments or other electronic device interfaced with an external system. Based on the user selected parameters, the communication interface block calls an appropriate constructor to create an instrument object or acquisition device object which is used to enable communication with the control instrument or acquisition device respectively. The instrument object/acquisition device object calls a software driver appropriate for the hardware interface of the control instrument/acquisition device. The use of a common interface block provides scalability and ease of use to the block diagram environment when interacting with control instruments and acquisition devices.

Abstract: In one embodiment, a test and measurement application executing on a computing device is interfaced with one or more external device coupled to the computing device. A device driver is selected for use with one of the external device from two or more available device drivers that are each compatible with the external device. The device driver is coupled to a virtual driver interface that provides the test and measurement application with a standardized interface to any of the two or more available device drivers. The test and measurement application communicates with the external device through the virtual driver interface.

Abstract: A method transfers data from a data source to multiple data sink objects. The data acquired from the data source is encapsulated into a data object. Identification information of the data object is posted to a data server. The data server shares the identification information with the data sink objects that are registered with the data server. The data sink objects access the data object with the identification information at execution time. A counter indicates the number of data sink objects that currently use the data object. The data object is removed from the memory of the computer systems when the counter indicates that the data object is no longer used by the data sink objects. Alternatively, the data object that is no longer used may be stored in a separate memory location of the computer systems for a future use.

Abstract: A communication system for linking users to control instruments. A user may send a first creation command from a user interface and establish a communication channel linking the command interpreter and the control instrument independent of the interface bus standard or interface hardware driver type. The communication system also includes providing a common communication interface between the user and the control instrument in an array-based programming environment. Embodiments provide a concise and powerful communication system for communicating with control instruments independent of the various types of supported interface bus standards, communication protocols, and driver types.

Abstract: In a computer-implemented method for running a test, the test to test a system under test is generated. At least a portion of the test is designated to be run as a distributed test. The designated test portion is selected to be run in one of a synchronous execution mode or an asynchronous execution mode. Tasks of the generated test are distributed to a plurality of workers. The distributed tasks are run with the plurality of workers according to the execution mode selection.

Abstract: In a computer-implemented method for transferring data, data is received from an external source, the data comprising a plurality of units. Each unit of the data is formatted into a formatted data unit having a first format. A full buffer is formed by storing the formatted data units in a data buffer. Contents of the full buffer is provided to an internal data sink, wherein the internal data sink is configured to provide the data units of the full buffer to a data converter, the data converter providing the data units to one or more external data sinks in an associated external data sink compatible format.

Abstract: An image acquisition facility for linking a user of an application to an image acquisition device independent of an interface protocol of the image acquisition device. The image acquisition facility establishes a communication channel between the user and the image acquisition device and manages communication across the established channel. In this manner, the user of the application is free to select a desired image acquisition device for interfacing with and interacting with the selected image acquisition device independent of the interface bus standard, communication protocol and driver type supported by the selected image acquisition device.

Abstract: A cross-platform interface tool provides a common interface for any hardware or software component having some advertising mechanism listing its features, input, and output requirements. The advertising mechanism can take a number of different forms, including data, a software object definition, or a communications system. The cross-platform interface tool includes a parsing mechanism for parsing through a component description associated with at least one of the plurality of components to gather information relating to the components. A component interface creator automatically generates a component interface based on the information gathered by the parsing mechanism.

Abstract: A cross-platform interface tool provides a common interface for any hardware or software component having some advertising mechanism listing its features, input, and output requirements. The advertising mechanism can take a number of different forms, including data, a software object definition, or a communications system. The cross-platform interface tool includes a parsing mechanism for parsing through a component description associated with at least one of the plurality of components to gather information relating to the components. A component interface creator automatically generates a component interface based on the information gathered by the parsing mechanism.