Patent Publication Number: US-2012026173-A1

Title: Transitioning Between Different Views of a Diagram of a System

Description:
PRIORITY INFORMATION 
     This application is a continuation-in-part of U.S. application Ser. No. 12/869,270, titled “Graphically Specifying and Indicating Targeted Execution in a Graphical Program”, filed Aug. 26, 2010, whose inventors were Jeffrey L. Kodosky, David W. Fuller III, Timothy J. Hayles, Jeffrey N. Correll, John R. Breyer, Jacob Kornerup, Darshan K. Shah, and Aljosa Vrancic, which is a continuation-in-part of U.S. application Ser. No. 11/776,196, titled “Diagram That Visually Indicates Targeted Execution”, filed Jul. 11, 2007, whose inventors were Jeffrey L. Kodosky, David W. Fuller III, Timothy J. Hayles, Jeffrey N. Correll, John R. Breyer, Jacob Kornerup, Darshan K. Shah, and Aljosa Vrancic, which claims benefit of priority of the following provisional applications: U.S. provisional application Ser. No. 60/942,834 titled “Diagram That Visually Indicates Targeted Execution” filed Jun. 8, 2007, whose inventors were Jeffrey L. Kodosky, David W Fuller III, Timothy J. Hayles, Jeffrey N. Correll, John R. Breyer, Jacob Kornerup and Darshan K. Shah; U.S. provisional application Ser. No. 60/869,221 titled “System Diagram that Illustrates Programs in a Distributed System Having Multiple Targets” filed Dec. 8, 2006, whose inventor was Timothy J. Hayles; and U.S. provisional application Ser. No. 60/821,512 titled “Execution Target Structure Node for a Graphical Program”, filed Aug. 4, 2006, whose inventors were Darshan K. Shah and Aljosa Vrancic. The above listed applications are hereby incorporated by reference in their entirety as though fully and completely set forth herein. 
    
    
     FIELD OF THE INVENTION 
     The present invention relates to the field of system diagrams, and more particularly to a system and method for presenting different views of a system diagram based on input from a user. 
     DESCRIPTION OF THE RELATED ART 
     Currently, many engineers design and use systems involving many different devices. Additionally, these different devices typically run or are configured according to disparate software programs that are deployed on or among multiple different devices. Accordingly, it is difficult for a designer or user of a system to fully understand all of hardware, physical interconnections, software, and software interconnections of such systems in an intuitive manner. Thus, improvements in understanding and designing systems are desired. 
     SUMMARY OF THE INVENTION 
     Various embodiments of a system and method for presenting different views of a system, e.g., based on gestures, are presented. 
     Initially, a first view of a first portion of the system may be displayed. For example, the system may include a plurality of devices and the first portion of the system may correspond to one of the devices. However, other embodiments are envisioned where the portion of the system includes more than one device, only a portion of a device, etc. For example, the system may be a single device system and/or the portion may be the entirety of the system. 
     User input requesting a different view of the first portion of the system may be received. Accordingly, a second view of the first portion of the system may be provided in response to the first gesture. 
     In some embodiments, the user input may be requested via a first gesture. The first gesture may be a translation gesture, e.g., a vertical translation gesture. The gesture may be a touch gesture, e.g., using one or more fingers on a touch surface, such as a touch display. Typically, the first gesture may be applied to the portion of the display showing the first view or portion of the system. For example, a user may provide a single touch vertical swipe gesture to a touch surface. However, other types of gestures are envisioned, including horizontal swipe gestures, multi-touch gestures, gestures using a mouse (e.g., involving a right click+movement, such as translational movements), etc. 
     The first view and the second view may vary according to levels of abstraction. For example, the first view may correspond to a first level of abstraction of the first portion of the system and the second view may correspond to a second level of abstraction of the first portion of the system. In some embodiments, the first level may be a higher level than the second level. For example, as the user provides the first gesture the level of abstraction may increase or decrease. In contrast, another gesture may allow the user to view levels of abstraction that decreases or increases (e.g., the opposite effect of the first gesture). There may be a plurality of different views and the first gesture may allow the user to view a deeper level of abstraction in succession while an inverse of the first gesture may allow the user to view a higher level of abstraction (e.g., to traverse in the opposite direction of the first gesture). Exemplary first gestures and inverse first gestures are vertical translation gestures in opposite directions, horizontal translation gestures in opposite directions, etc. 
     In one embodiment, the first view may correspond to an appearance of the first portion of the system (e.g., an image of the physical device or portion of the system), while the second view may visually indicate components of the first portion of the system (e.g., hardware components, such as in a hardware schematic). In another embodiment, the second view may visually indicate software deployed or executed by the first portion of the system. 
     Additionally, in changing from the first view to the second view, the method may automatically transition or morph the first view into the second view, e.g., to visually indicate correspondence of icons or portions of the first view to icons or portions of the second view. For example, the first view may include an image or icon of a device within the system and the second view may have icons representing software deployed to devices within the system. Accordingly, in transitioning from the first view to the second view, there may be visual indications indicating a correspondence between the device&#39;s icon and icons representing software (e.g., graphical programs) deployed on that device. For example, an animation may be provided that shows the icon representing the device changing into the icon(s) representing the software (e.g., changing in size, appearance, etc.). Similarly, the animation may show movement from the position of the device&#39;s icon to the icons representing the software. Alternatively, the software icons&#39; position and the device&#39;s icon position may be similar or proximate to each other. Thus, a first view may morph or visually transition into a second view. 
     In addition to showing different views of the first portion of the system, second input may be used to view different portions of the system. For example, a second gesture (e.g., a horizontal translation gesture) may change the view of the first portion of the system to a view of the second portion of the system (e.g., the same view or a default view, as desired). Accordingly, a view of the second portion may be displayed in response to the second gesture. Once the second portion of the system is displayed, the user may provide the first gesture to view different views of the second portion of the system, similar to the first portion described above. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       A better understanding of the present invention can be obtained when the following detailed description of the preferred embodiment is considered in conjunction with the following drawings, in which: 
         FIG. 1  illustrates a network system comprising two or more computer systems configured according to one embodiment; 
         FIG. 2  is a block diagram of an exemplary computer system, according to one embodiment; 
         FIGS. 3A and 3B  are screen shots of an exemplary graphical program according to one embodiment; 
         FIG. 4A  is a screen shot of an exemplary system diagram which corresponds to 
         FIGS. 3A and 3B ; 
         FIGS. 4B-4G  are screen shots of exemplary system diagrams according to some embodiments; 
         FIGS. 5A and 5B  are screen shots of a split view of a system diagram and a physical diagram according to one embodiment; 
         FIGS. 6A and 6B  are screen shots of a composite view of a system diagram and a physical diagram according to one embodiment; 
         FIG. 7  is a flowchart diagram illustrating one embodiment of a method for presenting different views of a system based on gestures; 
         FIGS. 8A-9C  are exemplary Figures corresponding to the method of  FIG. 7 ; 
         FIG. 10  is a flowchart diagram illustrating one embodiment of a method for transitioning from one view to another view; and 
         FIGS. 11A-11E  are exemplary Figures corresponding to the method of  FIG. 10 . 
     
    
    
     While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. 
     DETAILED DESCRIPTION OF THE INVENTION 
     Incorporation by Reference 
     The following references are hereby incorporated by reference in their entirety as though fully and completely set forth herein:
     U.S. Pat. No. 4,914,568 titled “Graphical System for Modeling a Process and Associated Method,” issued on Apr. 3, 1990.   U.S. Pat. No. 5,481,741 titled “Method and Apparatus for Providing Attribute Nodes in a Graphical Data Flow Environment”.   U.S. Pat. No. 6,173,438 titled “Embedded Graphical Programming System” filed Aug. 18, 1997.   U.S. Pat. No. 6,219,628 titled “System and Method for Configuring an Instrument to Perform Measurement Functions Utilizing Conversion of Graphical Programs into Hardware Implementations,” filed Aug. 18, 1997.   U.S. Pat. No. 7,042,469, titled “Multiple Views for a Measurement System Diagram,” filed Dec. 23, 2002.   U.S. Patent Application Publication No. 2001/0020291 (Ser. No. 09/745,023) titled “System and Method for Programmatically Generating a Graphical Program in Response to Program Information,” filed Dec. 20, 2000.   U.S. Patent Application Publication No. 2005/0050515 (Ser. No. 10/892,829) titled “A Graphical Program Which Executes a Timed Loop”, filed Jul. 16, 2004.   U.S. patent application Ser. No. 11/462,393 titled “Asynchronous Wires in a Graphical Programming System,” filed Aug. 4, 2006.   U.S. patent application Ser. No. 11/776,196, titled “Diagram That Visually Indicates Targeted Execution”, filed Jul. 11, 2007, whose inventors were Jeffrey L. Kodosky, David W. Fuller III, Timothy J. Hayles, Jeffrey N. Correll, John R. Breyer, Jacob Kornerup, Darshan K. Shah, and Aljosa Vrancic.   U.S. patent application Ser. No. 12/869,270, titled “Graphically Specifying and Indicating Targeted Execution in a Graphical Program”, filed Aug. 26, 2010, whose inventors were Jeffrey L. Kodosky, David W Fuller III, Timothy J. Hayles, Jeffrey N. Correll, John R. Breyer, Jacob Kornerup, Darshan K. Shah, and Aljosa Vrancic.   

     Terms 
     The following is a glossary of terms used in the present application: 
     Memory Medium—Any of various types of memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks  104 , or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; or a non-volatile memory such as a magnetic media, e.g., a hard drive, or optical storage. The memory medium may comprise other types of memory as well, or combinations thereof. In addition, the memory medium may be located in a first computer in which the programs are executed, or may be located in a second different computer which connects to the first computer over a network, such as the Internet. In the latter instance, the second computer may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computers that are connected over a network. 
     Carrier Medium—a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals. 
     Programmable Hardware Element—includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as “reconfigurable logic”. 
     Program—the term “program” is intended to have the full breadth of its ordinary meaning The term “program” includes 1) a software program which may be stored in a memory and is executable by a processor or 2) a hardware configuration program useable for configuring a programmable hardware element. 
     Software Program—the term “software program” is intended to have the full breadth of its ordinary meaning, and includes any type of program instructions, code, script and/or data, or combinations thereof, that may be stored in a memory medium and executed by a processor. Exemplary software programs include programs written in text-based programming languages, such as C, C++, Pascal, Fortran, Cobol, Java, assembly language, etc.; graphical programs (programs written in graphical programming languages); assembly language programs; programs that have been compiled to machine language; scripts; and other types of executable software. A software program may comprise two or more software programs that interoperate in some manner. 
     Hardware Configuration Program—a program, e.g., a netlist or bit file, that can be used to program or configure a programmable hardware element. 
     Diagram—A graphical image displayed on a computer display which visually indicates relationships between graphical elements in the diagram. Diagrams may include configuration diagrams, system diagrams, physical diagrams, and/or graphical programs (among others). In some embodiments, diagrams may be executable to perform specified functionality, e.g., measurement or industrial operations, which is represented by the diagram. Executable diagrams may include graphical programs (described below) where icons connected by wires illustrate functionality of the graphical program. Alternatively, or additionally, the diagram may comprise a system diagram which may indicate functionality and/or connectivity implemented by one or more devices. Various graphical user interfaces (GUIs), e.g., front panels, may be associated with the diagram. 
     Graphical Program—A program comprising a plurality of interconnected nodes or icons, wherein the plurality of interconnected nodes or icons visually indicate functionality of the program. A graphical program is a type of diagram. 
     The following provides examples of various aspects of graphical programs. The following examples and discussion are not intended to limit the above definition of graphical program, but rather provide examples of what the term “graphical program” encompasses: 
     The nodes in a graphical program may be connected in one or more of a data flow, control flow, and/or execution flow format. The nodes may also be connected in a “signal flow” format, which is a subset of data flow. 
     Exemplary graphical program development environments which may be used to create graphical programs include LabVIEW, DasyLab, DiaDem and Matrixx/SystemBuild from National Instruments, Simulink from the MathWorks, VEE from Agilent, WiT from Coreco, Vision Program Manager from PPT Vision, SoftWIRE from Measurement Computing, Sanscript from Northwoods Software, Khoros from Khoral Research, SnapMaster from HEM Data, VisSim from Visual Solutions, ObjectBench by SES (Scientific and Engineering Software), and VisiDAQ from Advantech, among others. 
     The term “graphical program” includes models or block diagrams created in graphical modeling environments, wherein the model or block diagram comprises interconnected nodes or icons that visually indicate operation of the model or block diagram; exemplary graphical modeling environments include Simulink, SystemBuild, VisSim, Hypersignal Block Diagram, etc. 
     A graphical program may be represented in the memory of the computer system as data structures and/or program instructions. The graphical program, e.g., these data structures and/or program instructions, may be compiled or interpreted to produce machine language that accomplishes the desired method or process as shown in the graphical program. 
     Input data to a graphical program may be received from any of various sources, such as from a device, unit under test, a process being measured or controlled, another computer program, a database, or from a file. Also, a user may input data to a graphical program or virtual instrument using a graphical user interface, e.g., a front panel. 
     A graphical program may optionally have a GUI associated with the graphical program. In this case, the plurality of interconnected nodes are often referred to as the block diagram portion of the graphical program. 
     Data Flow Graphical Program (or Data Flow Diagram)—A graphical program or diagram comprising a plurality of interconnected nodes, wherein the connections between the nodes indicate that data produced by one node is used by another node. 
     Physical Diagram—A diagram which visually indicates physical connectivity between physical devices. For example, a physical diagram may visually indicate the connectivity of various physical components in a measurement system, e.g., a computer connected to a measurement device via an Ethernet network. Thus the wires in a physical diagram represent physical connectivity between devices. A physical diagram may show the corresponding “real world” physical system/devices. 
     Configuration Diagram—A diagram which indicates connectivity between real and/or virtual devices. A configuration diagram may visually indicate physical connectivity between physical devices as shown in a physical diagram. However, in some embodiments, one or more of the devices (or all of the devices) in the configuration diagram may be virtual or simulated devices. Thus, some or all of the devices in the configuration diagram may not be physically present in the system represented by the configuration diagram. 
     System Diagram—A diagram with one or more device icons and graphical program code, wherein the device icons are use to specify and/or visually indicate where different portions of graphical program code are deployed/executed. A system diagram may indicate where (i.e., on which system/device) programs or code may be executed. For example, the system diagram may include graphical indications showing where portions of the displayed graphical program code are executed. In some embodiments, various ones of the icons may represent processing elements which have associated programs for execution. At least one of the icons may represent logical elements (e.g., executable software functions or graphical program code). One or more of the device icons may represent configurable elements. Thus, the system diagram may provide a system view which allows a user to easily understand where graphical program code is deployed among the various devices in the system. 
     Node—In the context of a graphical program, an element that may be included in a graphical program. The graphical program nodes (or simply nodes) in a graphical program may also be referred to as blocks. A node may have an associated icon that represents the node in the graphical program, as well as underlying code and/or data that implements functionality of the node. Exemplary nodes (or blocks) include function nodes, sub-program nodes (sub-Vis), terminal nodes, structure nodes, etc. Nodes may be connected together in a graphical program by connection icons or wires. The term “logical element” is used herein to refer to a “node”. For example, the term “logical element: may refer to a software program portion or code that is executable by (or implementable on) a processing element, and which is represented iconically on a display. Logical elements include virtual instruments (VIs), primitives, etc. Logical elements may be displayed in various ones of the diagrams described herein, e.g., in graphical programs, system diagrams, etc. 
     Wire—a graphical element displayed in a diagram on a display that connects icons or nodes in the diagram. The diagram may be a graphical program (where the icons correspond to software functions), a system diagram (where the icons may correspond to hardware devices or software functions), etc. The wire is generally used to indicate, specify, or implement communication between the icons. Wires may represent logical data transfer between icons, or may represent a physical communication medium, such as Ethernet, USB, etc. Wires may implement and operate under various protocols, including data flow semantics, non-data flow semantics, etc. Some wires, e.g., buffered data transfer wires, may be configurable to implement or follow specified protocols or semantics. Wires may indicate communication of data, timing information, status information, control information, and/or other information between icons. In some embodiments, wires may have different visual appearances which may indicate different characteristics of the wire (e.g., type of data exchange semantics, data transport protocols, data transport mediums, and/or type of information passed between the icons, among others). 
     Graphical User Interface—this term is intended to have the full breadth of its ordinary meaning The term “Graphical User Interface” is often abbreviated to “GUI”. A GUI may comprise only one or more input GUI elements, only one or more output GUI elements, or both input and output GUI elements. 
     The following provides examples of various aspects of GUIs. The following examples and discussion are not intended to limit the ordinary meaning of GUI, but rather provide examples of what the term “graphical user interface” encompasses: 
     A GUI may comprise a single window having one or more GUI Elements, or may comprise a plurality of individual GUI Elements (or individual windows each having one or more GUI Elements), wherein the individual GUI Elements or windows may optionally be tiled together. 
     A GUI may be associated with a diagram, e.g., a graphical program. In this instance, various mechanisms may be used to connect GUI Elements in the GUI with nodes or icons in the diagram/graphical program. For example, when Input Controls and Output Indicators are created in the GUI, corresponding nodes (e.g., terminals) may be automatically created in the diagram or graphical program. Alternatively, the user can place terminal nodes in the diagram which may cause the display of corresponding GUI Elements front panel objects in the GUI, either at edit time or later at run time. As another example, the GUI may comprise GUI Elements embedded in the block diagram portion of the graphical program. 
     Front Panel—A Graphical User Interface that includes input controls and output indicators, and which enables a user to interactively control or manipulate the input being provided to a program or diagram, and view output of the program or diagram, during execution. 
     A front panel is a type of GUI. A front panel may be associated with a diagram or graphical program as described above. 
     In an instrumentation application, the front panel can be analogized to the front panel of an instrument. In an industrial automation application the front panel can be analogized to the MMI (Man Machine Interface) of a device. The user may adjust the controls on the front panel to affect the input and view the output on the respective indicators. 
     Graphical User Interface Element—an element of a graphical user interface, such as for providing input or displaying output. Exemplary graphical user interface elements comprise input controls and output indicators 
     Input Control—a graphical user interface element for providing user input to a program. Exemplary input controls comprise dials, knobs, sliders, input text boxes, etc. 
     Output Indicator—a graphical user interface element for displaying output from a program. Exemplary output indicators include charts, graphs, gauges, output text boxes, numeric displays, etc. An output indicator is sometimes referred to as an “output control”. 
     Computer System—any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term “computer system” can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium. 
     Measurement Device—includes instruments, data acquisition devices, smart sensors, and any of various types of devices that are operable to acquire and/or store data. A measurement device may also optionally be further operable to analyze or process the acquired or stored data. Examples of a measurement device include an instrument, such as a traditional stand-alone “box” instrument, a computer-based instrument (instrument on a card) or external instrument, a data acquisition card, a device external to a computer that operates similarly to a data acquisition card, a smart sensor, one or more DAQ or measurement cards or modules in a chassis, an image acquisition device, such as an image acquisition (or machine vision) card (also called a video capture board) or smart camera, a motion control device, a robot having machine vision, and other similar types of devices. Exemplary “stand-alone” instruments include oscilloscopes, multimeters, signal analyzers, arbitrary waveform generators, spectroscopes, and similar measurement, test, or automation instruments. 
     A measurement device may be further operable to perform control functions, e.g., in response to analysis of the acquired or stored data. For example, the measurement device may send a control signal to an external system, such as a motion control system or to a sensor, in response to particular data. A measurement device may also be operable to perform automation functions, i.e., may receive and analyze data, and issue automation control signals in response. 
     Processing Element—A hardware component or device which is operable to execute software, implement code (e.g., program code), be configured according to a hardware description, etc. Processing elements include various processors and/or programmable hardware elements (e.g., field programmable gate arrays (FPGAs)), or systems that contain processors or programmable hardware elements, among others. For example, a processing element may refer to an individual processor in a computer system or the computer system itself. 
     Configurable Elements—Systems or devices that provide configurable functionality but do not themselves includes processors that process data. Configurable elements may produce and/or consume data that may be provided to or received from various processing elements. A configurable element may have or receive configuration data that specifies functionality of the configurable element. Configurable elements comprise data acquisition (DAQ) devices and/or other sensors/devices. 
     Gesture—A touch gesture or other gesture (e.g., using a mouse or other input device). For example, the user may provide a touch gesture using one or more fingers or may provide a mouse gesture using a mouse (e.g., by providing clicks or movements of the mouse while a click is depressed, among other types of mouse gestures). 
     As used herein, a “touch gesture” refers to a touch interaction with a touch interface. A touch gesture may include the use of one finger (or digit), two fingers (e.g., to perform two simultaneous touches), three fingers, four fingers, five fingers, etc. A touch gesture involving one touch (e.g., by a single finger or digit) may be referred to as a “single-touch gesture” and a gesture involving more than one touch (e.g., by a plurality of fingers or digits) may be referred to as a “multi-touch gesture”. Generally, a touch gesture is begun by initiating a touch and is ended when the touch is no longer present (e.g., when there is no longer any touch on the touch interface or when the initial touch is no longer on the touch interface). 
     Exemplary touch gestures include a single touch (e.g., a “tap” with a single finger), a double touch (e.g., a “double tap” with a single finger), a two finger touch (e.g., a “tap” using two fingers simultaneously), a three finger touch, a four finger touch, a five finger touch, an expansion gesture (e.g., a “reverse pinch” or “spread” where two touches are initiated and then the distance between the two touches are increased while both remain in contact with the touch interface, although more than two touches may be used, e.g., with three touches where at least one touch moves away from the other two touches), a minimization gesture (e.g., a “pinch” where two touches are initiated and then the distance between two touches are decreased while both remain in contact with the touch interface, although more than two touches are envisioned), a “drag” or “slide” gesture using one or more touches (e.g., where a single touch is initiated, then moved some distance along the touch interface, and then released), a “flick” gesture using one or more touches (e.g., where a touch is initiated and then quickly moved along the touch interface and released), a “press” gesture (e.g., where one or more touches are initiated and then held for a threshold amount of time, longer than a tap gesture), a “press and tap” gesture (e.g., where one or more touches are “pressed” and then a second one or more touches are “tapped”). 
     In some embodiments, gestures may include drawing or outlining. For example, a user may provide a gesture by touching the touch interface and then drawing a shape (e.g., an “L”, backwards “L”, a circle, a square, or any type of shape or sequence of lines). The user may create the shape using any number of simultaneous touches (e.g., using one finger, using two fingers, etc.) and each may be distinguishable from the next based on the number of touches and drawn shape. Thus, gestures may include outlines or drawings of shapes. Similar gestures can be achieved using a mouse. Generally, gestures described herein are more complex than simple single tap gestures. These gestures may be referred to as “complex gestures”. Accordingly, as used herein, a “complex gesture” is any gesture other than (or more complex than) a single tap (e.g., a single touch tap). Generally, a complex touch gesture includes a single touch and additional touch input (e.g., such as another touch for a two touch tap, additional movement for a drag, increased time for a “touch and hold” gesture, etc.). Additionally, any instance of a “gesture” used herein may refer to a “complex gesture” or “complex touch gesture”. 
     FIG.  1 —Networked Computer System 
       FIG. 1  illustrates a system including a first computer system  82  that is coupled to a second computer system  90 , where one or both of the computers are operable to execute a system diagram, e.g., a graphical program, according to embodiments of the present invention. The computer system  82  may be coupled via a network  84  (or a computer bus) to the second computer system  90 . The computer systems  82  and  90  may each be any of various types, as desired, the particular types shown in  FIG. 1  being exemplary only. For example, in some embodiments, the second computer  90  may be a “computer on a card” in a chassis or even installed in the first computer  82 . In another embodiment, the second computer may be a programmable hardware element, such as a field programmable gate array (FPGA), or other programmable logic. 
     As shown in  FIG. 1 , the computer system  82  (and/or  90 ) may include a display device operable to display the system diagram, e.g., the graphical program, as the system diagram is created and/or executed. The display device may also be operable to display a graphical user interface or front panel of the system diagram during execution of the system diagram. The graphical user interface may comprise any type of graphical user interface, e.g., depending on the computing platform. 
     The computer system  82  may include at least one memory medium on which one or more computer programs or software components according to one embodiment of the present invention may be stored. For example, the memory medium may store one or more graphical programs (or other types of programs) that are executable to perform the methods described herein. Additionally, the memory medium may store a development environment application, e.g., a graphical programming development environment application used to create and/or execute such graphical programs. The memory medium may also store operating system software, as well as other software for operation of the computer system. Various embodiments further include receiving or storing instructions and/or data implemented in accordance with the foregoing description upon a carrier medium. 
     The network  84  can also be any of various types, including a LAN (local area network), WAN (wide area network), the Internet, or an Intranet, among others. The computer systems  82  and  90  may execute a system diagram, e.g., a graphical program, in a distributed fashion. For example, in one embodiment, computer  82  may execute a first portion of the block diagram of a graphical program and computer system  90  may execute a second portion of the block diagram of the graphical program, as will be described in more detail below. As another example, computer  82  may display the graphical user interface of a graphical program and computer system  90  may execute the block diagram of the graphical program. 
     In one embodiment, the graphical user interface of the graphical program may be displayed on a display device of the computer system  82 , and the block diagram may execute on a device coupled to the computer system  82 . The device may include a programmable hardware element and/or may include a processor and memory medium which may execute a real time operating system. In one embodiment, the graphical program may be downloaded and executed on the device. For example, an application development environment with which the graphical program is associated may provide support for downloading a graphical program for execution on the device in a real time system. Of course, the graphical program may be distributed in other ways as desired. For example, various portions of the block diagram of the graphical program may be targeted for execution across multiple targets or platforms. 
     FIG.  2 —Computer System Block Diagram 
       FIG. 2  is a block diagram representing one embodiment of the computer system  82  and/or  90  illustrated in  FIG. 1 , or computer system  82  shown in  FIG. 2A  or  2 B. It is noted that any type of computer system configuration or architecture can be used as desired, and  FIG. 2  illustrates a representative PC embodiment. It is also noted that the computer system may be a general-purpose computer system, a computer implemented on a card installed in a chassis, or other types of embodiments. Elements of a computer not necessary to understand the present description have been omitted for simplicity. 
     The computer may include at least one central processing unit or CPU (processor)  160  which is coupled to a processor or host bus  162 . The CPU  160  may be any of various types, including an x86 processor, e.g., a Pentium class, a PowerPC processor, a CPU from the SPARC family of RISC processors, as well as others. A memory medium, typically comprising RAM and referred to as main memory,  166  is coupled to the host bus  162  by means of memory controller  164 . The main memory  166  may store the graphical program operable to be distributed across multiple execution targets, as well as a development environment for creating the graphical program, and for specifying its distribution over multiple execution targets. The main memory may also store operating system software, as well as other software for operation of the computer system. 
     The host bus  162  may be coupled to an expansion or input/output bus  170  by means of a bus controller  168  or bus bridge logic. The expansion bus  170  may be the PCI (Peripheral Component Interconnect) expansion bus, although other bus types can be used. The expansion bus  170  includes slots for various devices such as described above. The computer  82  further comprises a video display subsystem  180  and hard drive  182  coupled to the expansion bus  170 . 
     As shown, a device  190  may also be connected to the computer. The device  190  may include a processor and memory which may execute a real time operating system. The device  190  may also or instead comprise a programmable hardware element. The computer system may be operable to deploy a graphical program, or a portion of a graphical program, to the device  190  for execution of the graphical program on the device  190 . The deployed graphical program may take the form of graphical program instructions or data structures that directly represents the graphical program. Alternatively, the deployed graphical program may take the form of text code (e.g., C code) generated from the graphical program. As another example, the deployed graphical program may take the form of compiled code generated from either the graphical program or from text code that in turn was generated from the graphical program. Below are described various embodiments of a method for specifying and implementing directed or distributed execution of a graphical program. 
     FIGS.  3 A and  3 B—Exemplary Graphical Programs 
     As described above, a graphical program may include a block diagram portion and a graphical user interface portion. In some embodiments, the graphical user interface portion may be comprised within the block diagram portion. The block diagram portion may include a plurality of interconnected nodes or icons which visually indicate functionality of the graphical program. Each of the nodes may have one or more inputs and/or outputs for accepting and/or providing data to other nodes in the graphical program. Each of the nodes in the graphical program may represent software functions or executable code. In other words, the nodes in the graphical program may represent or comprise logical elements (e.g., virtual instruments (VIs), primitives, etc.). 
     The nodes in the graphical program may be interconnected by lines or wires which indicate that indicate that data are provided from a first node to a second node in the graphical program. In some embodiments, the wires may be connected to the terminals of nodes in the graphical program. The terminals may provide connection points for connecting the wires to a node, e.g., to individual inputs or outputs of the node. Additionally, as described herein, these wires may be configured (e.g., automatically or manually) to provide data synchronously or asynchronously using various data exchange semantics and/or data transfer mechanisms (among others). In some embodiments, wires which indicate transfer of data may be referred to as data transfer wires. 
     In some embodiments, the graphical program may include one or more structure nodes which indicate control flow among one or more nodes in the graphical program. For example, the graphical program may include a conditional structure node (e.g., to implement conditional branching, if statements, switch statements, signal routing, etc.), a looping structure node for implementing looping among one or more nodes (e.g., while loops, do while loops, for loops, etc.), and/or other control flow nodes. 
     Additionally, the graphical program may visually indicate where portions of the graphical program are executed. In one embodiment, the visual indication may include a rectangular box that contains a portion of graphical code. In some embodiments, this visual indication may be referred to as a target execution node or icon. The target execution node may have an interior portion where graphical program code that is targeted for execution on a device is contained. For example, a device icon that includes an interior portion that is designed to receive graphical program code may be referred to as a target execution node. Additionally, or alternatively, this node may be referred to as a execution target structure node, as described in U.S. Provisional Ser. No. 60/869,221 and incorporated by reference above. As described in this provisional application, the target execution node may include (e.g., may reference) contextual information that allows the graphical program code to be executed on a target device. 
     The graphical program may be created or assembled by the user arranging on a display (e.g., of the computer system  82 ) a plurality of nodes or icons and then interconnecting the nodes to create the graphical program. In some embodiments, the user may select icons and/or wires from various palettes shown in a development environment on the display. In response to the user assembling the graphical program, data structures may be created and stored which represent the graphical program. As noted above, the graphical program may comprise a block diagram and may also include a user interface portion or front panel portion. Where the graphical program includes a user interface portion, the user may optionally assemble the user interface on the display. As one example, the user may use the LabVIEW development environment to create the graphical program. 
     In an alternate embodiment, the graphical program may be created by the user creating or specifying a prototype, followed by automatic creation of the graphical program from the prototype. This functionality is described in U.S. patent application Ser. No. 09/587,682 titled “System and Method for Automatically Generating a Graphical Program to Perform an Image Processing Algorithm”, which was incorporated by reference in its entirety above. Further descriptions regarding automatic creation of graphical programs can be found in U.S. Patent Application Publication No. 2001/0020291 which was also incorporated by reference above. Thus, the graphical program may be created in other manners, either manually (by the user) or automatically, as desired. The graphical program may implement a measurement function that is desired to be performed by one or more devices or instruments (e.g., indicated by target execution icons). In other embodiments, the graphical program may implement other types of functions, e.g., control, automation, simulation, and so forth, as desired. 
       FIGS. 3A and 3B  illustrate exemplary portions of a graphical program according to one embodiment. As shown, the graphical program includes a plurality of interconnected nodes which visually indicates functionality of the graphical program. 
     Thus, the plurality of interconnected nodes may visually indicate functionality of the graphical program. In other words, during execution of the graphical program, the functionality represented by the plurality of interconnected nodes may be performed. 
     FIGS.  4 A- 4 G—Exemplary System Diagrams 
     A system diagram may refer to a diagram comprising one or more device icons and graphical program code, wherein the device icons are use to specify and/or visually indicate where different portions of graphical program code are deployed/executed. A system diagram may include icons or nodes that are connected by lines or wires, e.g., device icons connected to other device icons, a first graphical code portion connected to a second graphical code portion. 
     In a system diagram, a first node or icon may provide data on an output and a wire may connect the output of the node to an input of a second node. Similar to descriptions above, an icon or node providing data on an output may refer to a device executing code represented by the icon or node resulting in transferal of data to between or among the software representing the nodes. Note that the program code or functions represented by the icons may be executing on one device or among a plurality of devices. For example, a first device may be executing code of the first node and a second device may be executing code of the second node, and data may be transferred between the devices as indicated by the nodes and/or wires connecting the nodes. 
     Thus, the icons (nodes) in the system diagram may represent logical elements such as, for example, software functions or virtual instruments. Similar to the graphical programs described above, graphical indications may be displayed on the diagram which visually indicate where code represented by the various icons execute. For example, target execution icons may visually outline one or more of the icons and indicate that software represented by those icons execute on a specified target or device. Thus, a target execution icon may include one or more icons or nodes (e.g., in the interior portion of the target execution icon) and may indicate where the one or more icons or nodes are executed. For example, where the target execution icon represents a computer system, the icons or nodes inside the target execution icon may be executed by the computer system. Note that target execution icons may be automatically populated in the system diagram based on discovery of available devices, as desired. Alternatively, the user may include target execution icons by selecting types of devices (or classes of devices) or including template target execution icons and then configuring the target execution icons. 
     Note that the target execution icon may be “bound” or associated with a specific device. For example, the target execution icon may refer to a single device with a known address (e.g., IP address, bus address, etc.) and that icons or nodes within the target execution icon may be executed by that specific device during execution. The user may choose the specific device by selecting the device from a list of available devices (e.g., as automatically populated or detected by the development environment). For example, the user may configure the target execution icon (e.g., as described above) to select the appropriate device. Note that when a specific device is selected for the target execution icon, the target execution icon may be automatically displayed in the diagram with resources of the specific device visually represented. For example, if a specific microprocessor is selected, the available DMA channels of the processor may be automatically displayed in or on the target execution icon. For example, one or more terminals or wires may be displayed connected to or on the target execution icon which indicate the available DMA channels of the processor. Alternatively, or additionally, the resources of the execution device may be displayed in a palette, and the user may select and associate the resources with nodes in the target execution icon. The palette may indicate whether the resources are available (e.g., by being present or active) or not available (e.g., by not being present or being “grayed out” (or otherwise indicated)). Additionally, a programmable target (one that is able to be configured) may have a visual indication of that programmability (e.g., such as by having a white or open interior portion) whereas one that is not programmable may not have such an indication (e.g., may be grayed out or a different color). 
     Note that in some embodiments, one or more icons or nodes may be displayed outside of target execution icons. In such embodiments, the one or more icons or nodes may be executed by a default device, system, and/or processing element. For example, nodes outside of any target execution icons (or nodes/software functions not associated with target execution icons) may be executed by a controlling computer system or other processing element. The default processing element may be referred to as the implicit context or execution device of the diagram, whereas target execution icons explicitly define the context or execution device for nodes associated therewith. 
     In some embodiments, the devices represented in the system (e.g., processing elements, configurable elements, and/or other devices) may be physically present in the system or may be virtual (e.g., the devices may be simulated during execution of the system diagram) as desired. Additionally, these devices may operate according to the functionality visually represented by the icons in the system diagram which represent the devices. Note that the virtual devices of the system diagram may have an underlying model which is usable (e.g., executable) to simulate behavior of a real device corresponding to the virtual device. For example, the underlying model may be a graphical program or other executable code. Alternatively, or additionally, the virtual devices may represent devices that are desired and/or required for the system (e.g., according to user input). 
     Additionally, as described above regarding graphical programs, one or more GUIs may be associated with the system diagram (e.g., logical or physical components of the system diagram) which may be used during execution of the system diagram. In some embodiments, the GUI(s) may be associated with the graphical program portions that are executed by the various processing elements/devices. Thus, the GUI(s) may act as a front panel to the system diagram during execution (e.g., for receiving user input and displaying information regarding various variables, functions, devices, and/or sensors (among others) that execute or operate during execution of the system diagram). 
     Thus, the system diagram may allow for a logical view of a system as well as indications regarding execution targets of code represented in the system diagram. Further, in some embodiments, the system diagram may also indicate physical layouts of the system (e.g., physical connectivity as well as indications regarding execution of the logical elements of the diagram). In primary embodiments, the system diagram at least includes interconnected icons representing software (e.g., graphical program code) and one or more graphical indications (e.g., target execution icons) which indicate where these logical elements execute. 
     Similar to the descriptions above regarding assembly of a graphical program, system diagrams may be assembled manually (e.g., where the user selects icons and connects the icons using wires) or automatically (e.g., in response to user input specifying a desired functionality), as desired. Thus, a system diagram may be assembled manually or automatically and may include logical elements, processing elements, and/or configurable elements, as desired. 
     As shown,  FIGS. 4A-4F  illustrate exemplary system diagrams according to one embodiment. More specifically,  FIG. 4A  illustrates an exemplary system diagram which is similar to the portions of the graphical program shown in  FIGS. 3A and 3B . This system diagram is directed to a system that includes four different execution targets, specifically, a host computer and three FPGAs. Each of these targets is represented by a respective icon  400  (e.g., an execution target icon) that contains a respective graphical program or graphical program portion, in this embodiment, written in “G”, the graphical programming language of the LabVIEW graphical development environment provided by National Instruments Corporation, and referred to as a virtual instruments (VI), although it should be noted that the “G” used may be an extended version in accordance with the techniques and features disclosed herein. 
     As  FIG. 4A  indicates, a Master-Slave Host VI  602  is shown targeted for execution on host computer (e.g., controller) “8186 RT (10.1.198.163)”, as the lower “box” or icon is labeled. This host computer preferably executes a real time execution engine, such as LabVIEW RT, as the “RT” indicates. The Master-Slave Host VI is coupled to respective VIs targeted for execution on respective DAQ boards, specifically, R-Series DAQ boards, as provided by National Instruments Corporation. These three VIs are shown contained in respective icons (e.g., execution target icons), where the icon labeled “7831R (RIO0::INSTR)” contains a Master FPGA VI  404 , “7831R (RIO1::INSTR)” contains a first Slave FPGA VI  406 , and “7831R (RIO2::INSTR)” contains a second Slave FPGA VI  408 . Thus, the icons (e.g., execution target icons) may partition the diagram into regions or portions with targeted execution. 
     In an exemplary application, the host process (the Master-Slave Host VI executing on host computer “8186 RT (10.1.198.163)”) controls performance of data acquisition operations (reads/writes) by the three DAQ boards executing their respective VIs, e.g., stimulating and capturing responses from three units under test (UUT). In one exemplary embodiment, the execution targets may be implemented on respective PXI cards in a PXI chassis, although other implementations may be used as desired. 
     Additionally, as shown, the Master-Slave Host VI specifies a clock rate via the leftmost node labeled “rate”, and sends this rate via a buffered data transfer wire  603  to a clock node in the Master FPGA VI (in “7831R (RIO0::INSTR)”), labeled “F &amp; DC”, which operates to generate and send a logical or Boolean clock signal (a sequence of T/F values) to respective Analog Input and Analog Output nodes in 7831R (RIO0::INSTR)”, “7831R (RIO1::INSTR)”, and “7831R (RIO2::INSTR)”, where the Analog Input nodes are each labeled “AI0”, and the Analog Output nodes are each labeled “AO0”. Note that on/off control of this clock signal generation is via a switch node (shown just below and to the left of the clock node, which is itself controlled by the Master-Slave Host VI, as may be seen. As  FIG. 4A  shows, timing wires  401  connect the clock node to the switch node and to the Analog Input and Output nodes. 
     As  FIG. 4A  further shows, each of the Analog Input and Analog Output nodes is triggered on a rising edge of the clock signal, as indicated by rising signal edges displayed near the terminals of the nodes. On each rising edge of the clock signal, each Analog Output node may operate to receive a value from the Master-Slave Host VI and generate a corresponding analog signal that may, for example, be provided to a respective UUT. As may be seen, the Analog Output nodes are each coupled via a buffered data transfer wire  403  to a node, e.g., a function or analysis node, referred to simply as a function node for brevity, positioned in a while loop in the Master-Slave Host VI, where these three wires exit the VI on the right. Note that the while loop determines the rate that new data values are supplied to the Analog Output nodes (by the function node). The times when the Analog Output nodes consume this data and generate voltages corresponding to these data are controlled by the timing wire. If the time comes to consume a value and none is there, the Analog Output node may not produce a new voltage but rather may retain its previous output state. 
     Also on this rising edge of the clock signal, each Analog Input node may receive an analog signal, e.g., from the UUT, digitize the signal, and send the value (or values) to the Master-Slave Host VI. Similar to the Analog Output nodes, each Analog Input node is coupled to the function node via a respective wire, where, as may be seen, the wires enter from the top of the VI and couple to the node from the left. Thus, the function node may both control signals to be provided to the UUTs and receive (and possibly process and/or analyze) signals returned from the UUTs. 
     Note the (six) intervening lozenge-shaped elements  410  coupling the wires to the function node. These elements, which may be referred to as “semantic casts” or simply “casts”, may operate as interfaces between nodes that operate in accordance with data flow semantics and wires that do not operate in accordance with data flow semantics. For example, in the system diagram of  FIG. 7F , the wires connecting the Analog I/O nodes to the function node are buffered data transfer wires, where data placed on the wire may be stored in a temporary data structure, e.g., a FIFO, before being read from the wire. Thus, the data on or in the wire is buffered. This is in direct contrast to data flow wires, where the data placed on a wire in one cycle must be consumed (read) that same cycle. These casts may be configured to implement specified rules governing reads and writes of data on the wires. For example, in the case that the buffered data transfer wires use FIFOs, in the case where a FIFO is empty, the function node may be prevented from attempting to read from the wire, and so the cast may impose the rule that when a FIFO is empty, the while loop containing the function node may be halted until data are available again, although it should be noted that is but one example of such a rule. 
       FIG. 4B  illustrates an exemplary system diagram with two configurable device icons (representing the same device, NI PXI-6255) are connected to a target execution icon (representing the execution device, NI PXI-8176). As shown, each target execution icon/configurable device icon includes a single node (except for the icon in NI PXI-8176 which is displayed inside a while structure), and where the icons are interconnected by lines. The icon in each target execution icon may represent a plurality of icons which may be interconnected (e.g., the icon of the execution icon may be a VI or sub-VI).  FIG. 4C  illustrates an exemplary system diagram where the icons of the target execution icons are expanded, and where the ADC&#39;s in the NI PXI-6255 are connected by timing wires, and  FIG. 4D  illustrates an exemplary system diagram where a further sub-VI is expanded.  FIG. 4E  illustrates an exemplary system diagram where each target execution icon includes a single node, which, similar to  FIG. 4B , may represent a plurality of icons that may be interconnected (e.g., the icon of the execution icon may be a VI or sub-VI). 
     More specifically,  FIGS. 4B-4E  illustrate system diagrams where a first device (NI PXI-6255) stores a first portion of a graphical program that represents configuration of the device for communication with a second device (NI PXI-8176). In these cases, the second device then provides data (during execution) back to the first device. Thus,  FIGS. 4B-4E  show both physical and logical relationships among graphical program portions executing on two devices. 
       FIG. 4F  is an example system diagram that is directed to a distributed modeling according to one embodiment. More specifically, the system diagram of  FIG. 7F  specifies or implements a system where respective models are targeted for respective execution on two execution targets, as specified by respective icons  400  (e.g., execution target icons) labeled “ECU (Master)” and “Engine”. 
     As may be seen, the ECU (Master) icon contains a clock node, labeled uSec and displaying a clock signal symbol, which is configured to generate clock signals with a period of 1000 us (microseconds), and which may provide the clock signals to an ECU Model node, so labeled, via a timing wire (with a specified delay of 65 us)  601 . The ECU Model node represents or includes an ECU model that simulates or emulates an engine control unit, e.g., for controlling an engine. The clock node represents the time-triggered network as a clock source and is used to configure the network to produce the desired cycle time. One benefit of this approach is that it may make mapping the application to another communications topology easier, i.e., modifying the application to execute on a different physical system or infrastructure than a time-triggered network. For example, one may wish to execute the application on two R Series cards plugged into the same PCI bus, or on two computers connected by an ordinary network. As another example, one may wish to run the ECU model on one core and the Engine Model on another core of a dual core CPU. Since the time-triggered app in the prior art example of  FIG. 7G  is so specific to running on a time-triggered network, to run that app on these other topologies, with the same timing, would require discarding most if not all of the original program and writing another one. In contrast, using the approach described herein, only the clock node has to be remapped. 
     As  FIG. 4F  also shows, the Engine icon includes an Engine Model node, so labeled, that represents or includes an engine model that simulates or emulates an engine, e.g., an internal combustion engine. Note that the clock node in the ECU (Master) icon is also coupled to the Engine Model node via a timing wire  401 . The ECU Model node and the Engine Model node are connected via two buffered data transfer wires  403 , thus forming a feedback loop, where the ECU Model node provides input to the Engine Model node, and the Engine Model node&#39;s output is provided back to the ECU Model node as input. 
     Finally,  FIG. 4G  illustrates a system diagram which includes dialogs for specification of procedures in the system as a whole. As shown on the target execution icon 7831R, a dialog including “Reset”, “Start”, and “Stop” may be displayed and may be wired to configure the respective resets, starts, and stops of the system. As shown, the 7831R device may begin execution upon receiving a signal via the wire connected to the “start” portion of the dialog. Additionally,  FIG. 7G  illustrates an implicit context for the graphical program portions on the left and right hand side of the system diagram. In this case, these graphical program portions may be executed by a controlling computer system. 
     Thus,  FIGS. 4A-4G  illustrate exemplary system diagrams. 
     Exemplary Physical Diagram 
     As described above, a physical diagram may refer to a diagram which indicates physical connectivity between physical devices in a system. For example, the physical diagram may visually indicate the connectivity of various physical devices in a measurement system, e.g., a computer connected to a measurement device via an Ethernet network. A physical diagram may show how executable functionality (e.g., of a graphical program or system diagram) is implemented in the real world. Thus, in primary embodiments, the physical diagram includes a plurality of interconnected icons, where each icon in the physical diagram corresponds to a physical device. Additionally, following these embodiments, connections between the icons in the physical diagram represents physical connectivity. For example, the wires between the icons in the physical diagram may represent Ethernet cables, USB connections, Firewire connections, and/or other physical media which connects devices in the system. In some embodiments, physical diagrams (and/or system diagrams) may also be useful for visualizing variable, channel, or network relationships among devices in the system. Note that a certain type of wire may also be used to represent a wireless connection. 
     Note that in some embodiments, configuration diagrams may have a similar appearance and/or use as physical diagrams. However, configuration diagrams may refer to diagrams which are not linked to physical reality as are physical diagrams. For example, one or more of the devices in a configuration diagram may not be physically present in the system (e.g., it may be simulated or implement on other devices in the system). Thus, physical diagrams represent physical components and physical connectivity of a system and configuration diagrams may represent physical components and/or virtual (or desired) components. 
     In some embodiments, the physical diagrams/configuration diagrams may be automatically populated or created by performing a discovery process. For example, the development environment may automatically discover all coupled devices as well as the connectivity between the devices. Correspondingly, all of the physical devices may be displayed in the physical diagram/configuration diagram. Discovery may include not only the connectivity and presence of devices, but also their identities, configurations, available resources, and/or other characteristics. 
     An exemplary physical diagram is shown in the bottom portion of  FIGS. 5A and 5B  (described in more detail below). 
     FIGS.  5 A and  5 B—Synergy of Multiple Diagrams 
     In some embodiments, it may be desirable to display or use multiple diagrams. For example, graphical programs may allow users to see a logical view of a system. Similarly, system diagrams may provide an easy and intuitive means for visualizing the logical view of a systems as well as locations of execution and relationships between other physical or virtual devices of the system. Thus, a system diagram may allow a user to easily understand functionality and logical flow of execution over an entire system. Physical diagrams and/or configuration diagrams, on the other hand, may allow users to view the physical components and connectivity of the physical components. Thus, each of the various diagrams may provide different views of a system. 
     In some embodiments, it may be desirable to allow a user to choose one or more of these diagrams or “views” of the system. For example, the user may want to see a purely logical view of a system. In this example, a graphical program may be displayed for the user, e.g., on the computer system  82 . The graphical program may be displayed with or without graphical indications (e.g., target execution icons or configurable device icons) which visually indicate where portions of the graphical program are executed. Alternatively, the user may desire a system view of the system where both logical elements and execution indications are displayed. Additionally, the system view may include icons representing hardware devices (e.g., processing elements or configurable elements) that may not be present in the graphical programs. Finally, the user may want to view a physical representation of the system; correspondingly, the physical diagram may be displayed on the display of the computer system  82 . 
     In some embodiments, the multiple diagrams or views may each take up the entirety of the display. Thus, the user may, in one embodiment, toggle between the different views. Alternatively, the diagrams or views may be displayed in a “split view” where a plurality of diagrams or views are shown on the display, or the different diagram are shown separately and concurrently on multiple display devices. For example, in one embodiment, a split view may be displayed where a system diagram or graphical program is displayed in a top portion and the physical view (physical diagram) may be displayed on the bottom portion. In another example, in one embodiment, a split view may be displayed where a system diagram or graphical program is displayed on a first display device and the physical view (physical diagram) may be displayed on a second display device. This may be especially useful for conveying overall system information to the user. Thus, in one embodiment, the user may see a logical view of the system which may or may not indicate where logical elements execute as well as a physical view of the system allowing intuitive understanding of the entire system in one view. 
     In some embodiments, the development environment may allow the user to see correlations between the logical view and the physical view. For example, following the split view embodiment from above, a user may be able to select a physical component in the physical view and corresponding graphical indications in the logical view may be visually modified to indicate where graphical program portions execute. For example, the user may select a computer system in the physical view and one or more target execution icons (or possibly icons comprised in the target execution icons themselves) may “pop” (e.g., appear to jump or bounce on the screen), change colors, become highlighted, marching ants, and/or otherwise be visually indicated. Similarly, the user may select various components in the logical view and corresponding hardware devices in the physical view may be highlighted or visually indicated. Thus, the user may easily discern which logical elements in the system diagram or graphical program correspond to the physical devices shown in the physical diagram. 
     Additionally, the user may be able to associate elements in the physical view with elements in the logical view or vice/versa. For example, the user may select a physical device in the physical diagram and invoke creation of an icon in the system diagram/graphical program. In one embodiment, the user may simply select one of the device and drag that device into the system diagram to invoke creation of an icon (e.g., an execution target icon or configurable device icon) in the system diagram which corresponds to that device. Alternatively, the user may select various logical elements or nodes in the system diagram and associate those icons or nodes with the devices in the physical diagram. As one example, the user may select one or more icons (e.g., a graphical program portion) in the system diagram and associate the icons with a device in the physical diagram (e.g., by dropping the icons on the device). Correspondingly, a new target execution icon or configurable icon (among others) that is associated with the device may be displayed in the system diagram with the one or more icons. Additionally, the target execution icon or configurable icon may be displayed according to connectivity of the device in the system, if desired. 
     As shown,  FIGS. 5A and 5B  illustrate exemplary split views of a system diagram and a physical diagram. Note that these Figures correspond to the system diagrams illustrated in  FIGS. 4B-4E . As shown in  5 A, the top portion illustrates the system diagram of  FIG. 4B  and the bottom portion shows the physical connectivity between the two devices of the system (in this case from a port of a chassis to a computer). More specifically,  FIG. 5A  depicts a data streaming application where data is read from the PXI-6255, streamed over DMA to the PXI-8176, which after modifying the data, streams data back to the PXI-6255 to be output. The FIFO affordance of the wire is used as an access point for configuring buffering policies for the configurable wire. This Figure also illustrates the concept that a single physical device (in this case the PXI-6255) can have multiple logical representations 
     Similarly,  FIG. 5B  shows the same split view with an expanded system diagram (from  FIG. 4C ). Thus,  FIGS. 5A and 5B  show exemplary split views of a system diagram and physical diagram. 
     Note that the above described views are exemplary only and that other views are contemplated. For example, in some embodiments, there may be a single view, e.g., of a system diagram, where all physical and logical connectivity is indicated. Thus, in these embodiments, the user may easily understand the entirety of the system.  FIGS. 6A and 6B  illustrate exemplary diagrams of this case. As shown in  FIG. 6A , the cRIO-9014 Microprocessor is connected to cRIO-9103 which is connected to 9211. In this case, instead of separating the logical components of the cRIO-9014 and cRIO-9103 separate target execution icons, the physical and logical relationship is shown in a single view. Similarly,  FIG. 6B  shows this single view, but also shows the logic of the cRIO-9014. Note that in various embodiments, the user may switch between any of the views/diagrams described above, as desired. Additionally, the user may choose to “morph” any available view to another view. For example, the user may be viewing a physical diagram of the system and may invoke a “morph” or graphical change in the diagram to a different view, such as the combined view described above. Further embodiments related to morphing or transitioning between views are described below. Alternatively, the user may invoke a conversion of the physical diagram to a logical view or system diagram, as desired. Note that these views/changes are exemplary only and that others are envisioned. 
     Alternatively, or additionally, more than two diagrams may be shown simultaneously. For example, two or more of a physical diagram, a configuration diagram, a system diagram, and/or a graphical program (among other diagrams) may be displayed at the same time. In some embodiments, various ones of the diagrams may be overlaid in an intelligent manner, to convey an intuitive understanding of the system to the user. For example, when two or more diagrams are overlaid, corresponding nodes or icons in the different diagrams may be shown in the same position on the display to indicate correspondence. In one embodiment, a diagram may be automatically modified to allow this correspondence to be readily displayed. Thus, the above described views are exemplary other, and other views are envisioned. 
     In one embodiment, one or more of the above described diagrams may be used for mapping system configurations to existing system configurations. For example, in one embodiment, the user may wish to map a diagram (e.g., containing specified physical and logical elements) to an existing (physical) system. For example, the existing diagram may have physical components (e.g., devices) which differ from the user&#39;s existing (physical) system. The development environment may be able to map the diagram (e.g., automatically) to the existing system and/or simulate the missing devices that are indicated in the diagram. Thus, diagrams may be mapped onto real systems by transferring functionality to existing systems or via simulation of the missing components (among others). 
     Thus,  FIGS. 3A-6B  illustrate exemplary diagrams/views of systems. The following sections describe configuration and display of data transfer functionality in the various diagrams described above (among others). 
     FIG.  7 —Presenting Different Views of a System Diagram Based on Gestures 
       FIG. 7  illustrates a computer-implemented method for presenting different views of a system diagram based on gestures from a user. The method shown in  FIG. 7  may be used in conjunction with any of the computer systems or devices shown in the above Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, performed in a different order than shown, or omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows. 
     In  702 , a first view of a first portion of the system may be displayed. For example, the system may include a plurality of devices and the first portion of the system may correspond to one of the devices. However, other embodiments are envisioned where the portion of the system includes more than one device, only a portion of a device, etc. For example, the system may be a single device system and/or the portion may be the entirety of the system. 
     In  704 , user input specifying a first gesture may be received. The first gesture may be used to request a different view of the first portion of the system. Accordingly, in  706 , a second view of the first portion of the system may be provided in response to the first gesture. 
     In some embodiments, the first gesture may be a translation gesture, e.g., a vertical translation gesture. The gesture may be a touch gesture, e.g., using one or more fingers on a touch surface, such as a touch display. The touch display may be provided as a peripheral to a computer system (such as those shown in  FIG. 1 ) or may be provided as a display of the computer system (e.g., for a touch surface system). The touch surface may detect the touches or gestures according to any of various methods, such as capacitive sensing, IR cameras, etc. 
     Typically, the first gesture may be applied to the portion of the display showing the first view or portion of the system. For example, a user may provide a single touch vertical swipe gesture to the portion of a touch display showing the first view. Other types of gestures are envisioned, including horizontal swipe gestures, multi-touch gestures, gestures using a mouse (e.g., involving a right click+movement, such as translational movements), etc. In general, any of the gestures described above may be used to change from the first view to a second view, among others, as desired. In some embodiments, the gesture may be applied to other areas, rather than the portion of the display showing the first view or portion of the system. For example, the touch gesture may be received to a different area of the display, via an external touch surface, to a dedicated gesture portion of the touch display or surface, etc. When applied to such areas, the touch gesture may be interpreted based on the context of the gesture (e.g., based on what icons or areas within the application are selected, based on the current view, etc.). 
     The first view and the second view may vary according to levels of abstraction. For example, the first view may correspond to a first level of abstraction of the first portion of the system and the second view may correspond to a second level of abstraction of the first portion of the system. In some embodiments, the first level may be a higher level than the second level. For example, as the user provides the first gesture the level of abstraction may increase. In contrast, another gesture, such as an inverse or opposite gesture, may allow the user to view levels of abstraction that decreases (e.g., the opposite effect of the first gesture). There may be a plurality of different views and the first gesture may allow the user to view a deeper level of abstraction in succession while an inverse of the first gesture may allow the user to view a higher level of abstraction (e.g., to traverse in the opposite direction of the first gesture). Exemplary first gestures and inverse first gestures are vertical translation gestures in opposite directions, horizontal translation gestures in opposite directions, etc. 
     In one embodiment, the first view may correspond to an appearance of the first portion of the system (e.g., an image of the physical device or portion of the system), while the second view may visually indicate components of the first portion of the system (e.g., hardware components, such as in a hardware schematic). In another embodiment, the second view may visually indicate software deployed or executed by the first portion of the system. Other types of views are envisioned, such as any of those described above, e.g., physical views, system diagram views, configuration view, graphical programming view, etc. Thus, a user may view different views of portion(s) of a system using gestures. 
     In addition to showing different views of the first portion of the system, in  708 , a second gesture may be used to view different portions of the system. For example, a second gesture (e.g., a horizontal translation gesture) may change the view of the first portion of the system to a view of the second portion of the system (e.g., the same view or a default view, as desired). Accordingly, in  710 , a view of the second portion may be displayed in response to the second gesture. Once the second portion of the system is displayed, the user may provide the first gesture to view different views of the second portion of the system, similar to the first portion described above. 
     The method of  FIG. 7  may apply to various views of an entire system, e.g., switching between physical views, system diagram views, software views, etc. For example, a user may view the system in a system diagram view where devices and deployed software are visually indicated and then may switch to viewing the system in a physical view where physical devices and physical interconnectivity is shown. However, in further embodiments, such as those shown in  FIGS. 8A-9D , the user may invoke views of the system (or portions of the system) from within a user interface, e.g., specific to devices within the system. Accordingly, the method of  FIG. 7  may be applied to diagrams of an entire system where icons represent software, hardware, etc., or may be separately used within a separate user interface, e.g., to browse through portions of a system and views of those portions of the system. 
     FIGS.  8 A- 9 D—Exemplary Figures Correspond to the Method of FIG. 7 
       FIGS. 8A-8C  are exemplary Figures corresponding to viewing different portions of a system and  FIGS. 9A-9D  are exemplary Figures corresponding to different views of a portion of a system. 
     More specifically, as shown in  FIG. 8A , a graphical user interface (GUI) may be shown, where the user may be able to select “device” in order to view the devices in a system. The user may also be able to view other interfaces or views, including photo, wiring, software, etc. In some embodiments, these other views may allow the user to examine the entire system (or a larger portion of the system) rather than individual devices. For example, if “photo” is selected, photographs of the devices may be shown in a connected diagram, e.g., similar to a physical view. Similarly, wiring and software may show other views of the system. 
     As also shown in  FIG. 8A , the devices include a chassis on the left, a selected computer card (e.g., PC on a card) for inclusion in the chassis, and a data acquisition card for inclusion in the chassis. In  FIG. 8B , the user may provide a single touch right to left swipe to change from viewing the computer card to viewing the data acquisition card. As shown in  FIG. 8C , the result of the touch gesture provided in  FIG. 8B , the data acquisition card is selected and the PC card is displayed on the left hand side. However, the chassis has now disappeared from the GUI. The user could provide an inverse gesture (in this case, a single touch left to right swipe) to return to selecting the computer card. 
       FIG. 9A  is the same as  FIG. 8C . In  FIG. 9B , the user may provide a single touch top to bottom swipe to change views of the data acquisition card. As shown in  FIG. 9C , instead of showing an image of the data acquisition card, a schematic diagram of the data acquisition card is shown. More specifically, there is an adaptor module portion of the data acquisition card and a programmable portion of the data acquisition device. In response to providing the same gesture as in  FIG. 9B , a new view of the data acquisition card is shown in  FIG. 9D . More specifically, in this diagram the software deployed on the programmable portion is displayed. In this case, the graphical programs “PLL.vi”, “Wave Shaper.vi”, and “PID.vi” are deployed on the programmable portion of the data acquisition card. As shown, the “PLL.vi” and “Wave Shaper.vi” graphical programs are coupled to the “AC In” and “Switches” portions of the adaptor module. In response to the same gesture, another view could be displayed, e.g., showing the details of the graphical program deployed on the data acquisition card. Contrarily, providing an opposite or inverse gesture (in this case a bottom to top touch swipe), the user could return to previous views of the data acquisition card. Note that while this example shows only views for a single device, it may be extended to more than one device in the system, the entirety of the system, etc. For example, gestures could be used to switch from viewing a logical view of the system, a physical view of the system, a system diagram view of the system, etc. As described below, each view may morph or transition from one to another. 
     FIG.  10 —Transitioning Between Different Views of a System 
       FIG. 10  illustrates a computer-implemented method for transitioning or morphing between different views of a system. The method shown in  FIG. 10  may be used in conjunction with any of the computer systems or devices shown in the above Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, performed in a different order than shown, or omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows. 
     In  1002 , a first view of a first portion of the system may be displayed. Displaying the first view of the first portion of the system may be similar to  702 , described above. As previously described, the first view may be any of various views and the first portion of the system may be the entirety of the system, one or more devices of the system, etc. 
     In  1004 , user input requesting a different view of the first portion of the system may be received. The user input can be received in any number of ways. For example, the user may provide a gesture as in  704  above. However, other types of input are envisioned, e.g., using a mouse to select a different view, a key combination, or any type of user input to request the different view of the first portion of the system. 
     Accordingly, in  1006 , a second view of the first portion of the system may be provided in response to  1004 . The second view may be similar to that presented in  706 , described above. Additionally, in changing from the first view to the second view, the method may automatically transition or morph the first view into the second view, e.g., to visually indicate correspondence of icons or portions of the first view to icons or portions of the second view. 
     For example, the first view may include a first plurality of icons and the second view may include a second plurality of icons. Some or all of these icons may have a correspondence between each other. For example, respective ones of the first plurality of icons may correspond to respective ones of the second plurality of icons. Accordingly, transitioning from the first view to the second view may visually indicate that correspondence. This visual indication may be achieved in a variety of manners. 
     For example, the first view may include a first icon that corresponds to one or more second icons in the second view. In order to indicate a correspondence between the first icon and the second icon(s), the position of the first icon and the position of the second icon(s) may be the same or approximately the same. More specifically, in one embodiment, if the first view and the second view were overlaid, they may appear in the same position or proximate to each other. The position being “approximately the same” or being “proximate” to each other refers to the location being similar enough between the two views that a user would identify a correspondence. For example, if overlaid, at least a portion of the icons may overlap, the icons may be within a few pixels, 10 pixels, 30 pixels, 50 pixels, etc., depending on the resolution of the display. 
     Alternatively, the first icon and the second icon(s) may be in different positions in the respective views. Accordingly, the visual indication may be provided via an animation. For example, the animation may show movement from the location of the first icon to the location of the second icon(s) in order to indicate their correspondence. Additionally, the animation may show the first icon changing into the second icons. Where there are a plurality of icons, the animation may show the first icon splitting into the second icons while moving from the location of the first icon to the location of the second icons. Similarly, where the size of the first icon and second icon(s) are different, the animation may indicate a change in size, e.g., the first icon growing larger or smaller while changing into the second icon(s). Note that the animation may be used even when the first and second icon(s) are in similar positions. Thus, a visual indication, such as an animation may be used to show that various ones of the icons in the first view correspond to respective ones in the second view. Note that some of the icons in the second view may not correspond to icons in the first view. Accordingly, there may not be a visual indication of correspondence for these icons. Similarly, there may not be a visual indication of correspondence for icons in the first view that do not correspond to icons in the second view. 
     As a more specific example, the first view may include an image or icon of a device within the system and the second view may have icons representing software deployed to devices within the system. Accordingly, in transitioning from the first view to the second view, there may be visual indications indicating a correspondence between the device&#39;s icon and icons representing software (e.g., graphical programs) deployed on that device. For example, an animation may be provided that shows the icon representing the device changing into the icon(s) representing the software (e.g., changing in size, appearance, splitting from one icon into a plurality of icons, etc.). Similarly, the animation may show movement from the position of the device&#39;s icon to the icons representing the software. Alternatively, as indicated above, the software icons&#39; position and the device&#39;s icon position may be similar or proximate to each other. Thus, a first view may morph or visually transition into a second view. 
     While the above descriptions use the term “icon”, various embodiments may act on any blocks or images within each view. In other words, the method of  FIG. 10  is not limited to only icons. Additionally, the term “icon” generally refers to an image that represents an object, whether it be physical, in software, etc. For example, icons may represent physical devices and/or connections between devices, software programs (e.g., graphical programs), etc. Further, icons may have interior portions; thus, an icon may include other icons. 
     FIGS.  11 A- 11 E—Exemplary Figures Corresponding to the Method of FIG. 10 
       FIGS. 11A-11E  are exemplary figures corresponding to the method of  FIG. 10 . More specifically, the diagrams shown in  FIGS. 11A-11E  correspond to different views and transitions between views of a prototype system for an embedded control unit in an electric vehicle. This embedded control unit may be implemented as a “smart charger” that can make adjustments based on the load on the power grid (e.g., daily peaks in usage). 
       FIG. 11A  presents a “functional block diagram” (also referred to as a “whiteboard sketch”) view of the system. This diagram describes how the system works at a very high level. The functionality is not restricted to specific hardware or specific implementations (code). As shown, the system may use various data, e.g., from the utility company (such as load on the grid, customer accounts, billing systems, etc.) and/or the EV company (e.g., battery charge, GPS locator, etc.). In addition, a user interface may be configured to receive the data from the EV company. Further, the data from the utility company may be provided to a utility SCADA communicator which may in turn be coupled to an AC/DC switch. The AC/DC switch may also be coupled to an AC power grid and an inverter/rectifier of the vehicle. The car may also include an EV battery, motor/generator, and power train. A control system, including charge control and supervisory control may be coupled to the motor/generator and inverter/rectifier as well as the two data sources. 
     While in this view, the user may choose to view another view, such as a component diagram. Accordingly, the functional block diagram view may morph into the component diagram.  FIG. 11B  shows the transition between the functional block diagram view of  FIG. 11A  and the component diagram view of  FIG. 11C . 
     As shown,  FIG. 11C  is a “component diagram” that shows a photo of each device or component in the system. In this view, the user may be able to see the physical components (e.g., devices) that perform the functionality shown in  FIG. 11A . As shown, the component diagram shows a picture of an AC grid (power lines), a wall-mount EV charging dock, a test vehicle, a vehicle-to-grid controller prototype, a customer application (shown as a phone), and the utility company and EV manufacturer data in the cloud. 
     In the exemplary transition between  FIGS. 11A and 11C , the blocks of  FIG. 11A  move to the corresponding components in  FIG. 11C  and then change into the components shown in  FIG. 11C . Thus, by showing the movement of the objects in the diagram to new positions and changing those objects into the objects of the component diagram of  FIG. 11C  (thereby morphing from one view to another), the user receives a visual indication of the correspondence of objects between the two views. In this particular transition, the AC power grid block moves to the location of the power lines image, the utility SCADA communicator and AC/DC switch move to the location of the wall-mount EV charging dock, the EV battery, inverter/rectifier, motor/generator, and power train move to the location of the test vehicle, the supervisory control and charge control move to the location of the vehicle-to-grid controller prototype, the two data sets move to their new positions, and the remote control UI moves to the location of the customer application. 
       FIG. 11E  is an “Implementation Diagram” that shows the code behind each element in the system. Some code is described as software programs (e.g., Web Service, VI, EXE). Other code is documented with an image representing a hardware circuit (e.g., battery, switch, etc.). While the hardware implementations are shown with a representational image, the user may be able to drill into that part of the diagram to reveal more details (e.g., the complete circuit), just as the user can drill into a VI node and see the graphical code behind it. 
     As with the last transition, in changing from the component diagram view of  FIG. 11C  to the implementation diagram of  FIG. 11E ,  FIG. 11D  shows the components of  FIG. 11C  moving to the position of corresponding objects in  FIG. 11D . More specifically, as shown, the AC power grid moves to the position of AC power, the EV charging dock moves to the position of the EV charging dock block (including utility client and local display), the test vehicle moves to the position of the test vehicle block (including power electronics, motor/generator, battery pack, and power train), the vehicle-to-grid control prototype moves to the position of the same block (including the PXIe FlexRIO and PXIe-8133 controller with corresponding graphical programs), the utility company data moves to the position of the utility company cloud (with customer accounts and grid load portions), the EV manufacturer data moves to the position of the vehicle MFG cloud, and the customer application moves to the position of the mobile platform (with a user interface executable). 
     Thus, similar to the transition between  FIGS. 11A and 11C ,  FIG. 11D  provides an exemplary transitory image between the views of  FIGS. 11C and 11E . Note that the full transition may include many more images, e.g., showing the full movement of the objects and connections as they move to their new positions and then change into the new objects. Additionally, while in these exemplary figures, the original objects do not change during movement, other embodiments are envisioned where the objects change while moving, split into more objects (as necessary) while moving, or any of the embodiments described above. 
     Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.