Applying successive data group operations to an active data group
This is a continuation of application Ser. No. 08/078,483, filed Jun. 16, 1993, now abandoned, which was a continuation of application Ser. No. 07/599,619, filed Oct. 18, 1990, now abandoned. 
     This is a continuation-in-part of U.S. patent application Ser. No. 08/099,047, filed on Jul. 28, 1993, now abandoned. 
    
    
     BACKGROUND OF THE INVENTION 
     The present invention is directed to user interfaces for data processing systems. It finds particular, although not exclusive, use in data processing systems used for complex simulations. 
     The capabilities of data processing systems have greatly advanced over the past several decades, and the amount of information that they can produce has similarly expanded. But the usefulness of the resulting information can depend to some degree on the ease with which the user can locate desired information in the mass of information that results. 
     Among the areas in which this is particularly true is that of simulation. Computer simulations have been employed on a wide variety of systems, such as electronic circuits, weather patterns, national economies, and manufacturing plants. All simulations depend on models, i.e., statements of relationships among the variables employed in the simulation. Once a model has been written, the data processing system performs the actual simulation; it computes series of values of the simulation variables as functions of an independent variable, typically time. 
     One obvious reason for performing a simulation is simply to predict performance, i.e., to answer questions such as, What will XYZ Corporation&#39;s revenues be for the next 18 months? In this case, the variable of interest is revenues while the independent variable is time. 
     But a simulation often is used not simply to determine what a result will be but also to determine why the results are what they are and, generally, to obtain insight into the operation of the simulated system. For these purposes, the user often must investigate values of variables other than those of a small number of ultimate result variables. This in turn requires that the user determine which of the possibly thousands of variables he should inspect. These questions require the insight of the human user and often a significant level of concentration, which may not be achievable if too much of the user&#39;s attention must be devoted to the mechanics of the interface between the user and the data processing system. 
     SUMMARY OF THE INVENTION 
     The present invention provides an efficient, natural interface between the user and that part of the data processing system that presents data to the user. A data processing system according to the present invention includes a memory for storing data groups, such as the simulation results for different variables in the model of a simulated system. Each data group is associated with a different group name, which may be the same as the name of the variable whose simulation results the data group contains. The data processing system includes means for displaying the names of data groups and for displaying the &#34;tool symbols&#34; associated with respective data-group operations. The user employs some type of input means, such as a mouse, to designate a displayed data-group name and tool symbol. In response, the data processing system performs the operation represented by the tool symbol on the data group represented by the designated name. We have found that this provides a very natural user interface, particularly when the data processing system is used for simulation. 
     The data-group operations represented by the tool symbols may include, for instance, displays of the names and graphs of the values of the variables that are the &#34;causes&#34; of the variable whose name the user designates. By observing the cause graphs, the user can determine which of the causes is of greatest interest, and he can use a mouse or other input device to designate the name of that cause variable and specify the cause-graphing tool again. By repeating these functions, he can investigate the system in a natural manner. The user can thus maximize his concentration on the actual investigation rather than on the mechanics of requesting that the computer present the needed information. 
     The accompanying claims define these and further features of the invention with more precision. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     These and further features and advantages of the present invention are described by reference to the accompanying drawings, in which: 
     FIG. 1 is a block diagram of a simulation system in which the teachings of the present invention might be employed; 
     FIG. 2 is a representation of a display that such a system might present to a user to display the data-group names and tool symbols by which the user communicates with the system; 
     FIG. 3 is a representation of the display that results when the user employs the graphing operation provided by the illustrated embodiment of the invention; 
     FIG. 4 is a representation of the display that results when the user employs the causes operation; 
     FIG. 5 is a representation of the display that results when the user employs the causal-tree operation; 
     FIG. 6 is a representation of the display that results when the user employs the loops operation; and 
     FIG. 7 is a representation of the display that results when the user employs the outline operation. 
    
    
     DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT 
     FIG. 1 depicts in diagrammatic form a simulation system of the type that can embody the teachings of the present invention. Such a system typically includes a computer, which FIG. 1 symbolizes by the contents of the computer&#39;s memory, represented by dashed lines 12. 
     Appropriate input devices such as a keyboard 14 and a mouse 15 are coupled to the computer. The keyboard is depicted in such a manner as to represent its use to enter a simulation model, while the mouse 15 is so depicted as to suggest its use to control the presentation of simulation results. But both input devices can be used for either or both functions. 
     Among the computer&#39;s software modules is a pre-compiler 18. The pre-compiler 18 is the programming that enables the computer 12 to perform a number of functions having to do with the appropriate interpretation of the information that the user enters by way of the keyboard 14 to define the simulation model. The entries made from the keyboard 14 are ultimately compiled into object code--i.e., into machine-language instructions. 
     In theory, a single program could be used to make a direct conversion from the user&#39;s modeling language to the machine language that the computer hardware employs. But FIG. 1 depicts the software in its more typical, two-part form, in which a pre-compiler 18 recognizes the simulation language and converts it into source code of a compiler language, such as C, and a compiler 20 converts the source code into machine code. In addition to converting the simulation language into C, the pre-compiler 18 may also create cause and effect lists in a manner described in more detail in U.S. patent application Ser. No. 08/099,047,  of William T. Wood for A Simulation System Employing Causal Tracing, which was filed on Jul. 28, 1993, and assigned to the assignee of the present invention. 
     As that application describes in more detail, the simulation model is written as a set of equations typically entered from the keyboard by the user. Each of the equations defines a relationship between an effect variable and each of the variables that are its proximate causes. The effect variable in an equation is a proximate effect of each of the cause variables in that equation. The cause and effect lists include a list of all of the proximate causes of each variable as well as a list of all of its proximate effects. These lists are used during the presentation of the results in a manner described briefly below and in more detail in the Wood application. 
     The machine code generated by the compiler module 20 is a simulation program 24, which the computer 12 runs to generate simulation results 26. The results typically take the form of series of values of the various variables as functions of time. To investigate the results and the model, the user employs the mouse 15 to interact with a presentation module 28, which controls the display device 16. 
     To illustrate the operation of the invention, let us suppose that the computer 12 is to simulate the activity in a bank&#39;s accounts. To provide a model for such activity, the user may begin with an entry such as the following: 
     
         __________________________________________________________________________
BALANCE[CLIENT] = INTEG(MONEY.sub.-- IN[CLIENT] - MONEY.sub.-- OUT[CLIENT]
       INITIAL.sub.-- BALANCE[CLIENT])                                    
.sup.˜ dollars                                                      
.sup.˜ The total money in the bank balances of the clients.         
|                                                                
MONEY.sub.-- IN[CLIENT] = INTEREST[CLIENT] + DEPOSITS[CLIENT]             
.sup.˜ dollars/week                                                 
.sup.˜ The total money in each account at the start of a            
  simulation.                                                             
|                                                                
MONEY.sub.-- OUT[CLIENT] = WITHDRAWALS[CLIENT] + FEES[CLIENT]             
.sup.˜ dollars/week                                                 
.sup.˜ The total money leaving the bank account each time           
  period.                                                                 
|                                                                
INITIAL.sub.-- BALANCE[MARY] = 700.sup.˜˜                     
|                                                                
INITIAL.sub.-- BALANCE[JOHN] = 700                                        
.sup.˜ dollars                                                      
.sup.˜ The initial money in each account at the start of a          
  simulation.                                                             
|                                                                
INTEREST[CLIENT] = BALANCE[CLIENT] * INTEREST.sub.-- RATE[CLIENT]         
.sup.˜ dollars                                                      
.sup.˜ The interest payment received.                               
|                                                                
INTEREST.sub.-- RATE[CLIENT] =                                            
                 FIRST.sub.-- IF.sub.-- TRUE(BALANCE[CLIENT] &lt;1500,       
                 LOW.sub.-- INTEREST.sub.-- RATE,                         
                 HIGH.sub.-- INTEREST.sub.-- RATE) / 100                  
.sup.˜ dimensionless                                                
.sup.˜ The fractional rate of interest, which depends on the        
  amount of money in the bank.                                            
|                                                                
LOW.sub.-- INTEREST.sub.-- RATE = 8.00                                    
.sup.˜ dimensionless                                                
.sup.˜ The interest rate in percent if the balance is below         
  $1,500.                                                                 
|                                                                
HIGH.sub.-- INTEREST.sub.-- RATE = 9.00                                   
.sup.˜ dimensionless                                                
.sup.˜ The interest rate in percent if the balance is above         
  $1,500.                                                                 
|                                                                
DEPOSITS[MARY] = 600.sup.˜˜                                   
|                                                                
DEPOSITS[JOHN] = 450                                                      
.sup.˜ dollars/week                                                 
.sup.˜ The weekly salaries deposited into their accounts.           
|                                                                
WITHDRAWALS[MARY] = 475.sup.˜˜                                
|                                                                
WITHDRAWALS[JOHN] =  300                                                  
.sup.˜ dollars/week                                                 
.sup.˜ The amount of money taken out of the account each            
  week.                                                                   
|                                                                
FEES[CLIENT] = FIRST.sub.-- IF.sub.-- TRUE(BALANCE[CLIENT] &lt;1000,         
0.50,0)                                                                   
.sup.˜ dollars/week                                                 
.sup.˜ If the balance goes below $1000, a $2 per month fee is       
  charged. |                                                     
__________________________________________________________________________
 
    
     The first entry in the simulation defines relationships for two variables. Since the subscript CLIENT can have two values, namely, MARY and JOHN, the first entry essentially represents two equations, one in which the value of the subscript in all of the subscripted variables is MARY and the other in which it is JOHN. 
     The first statement specifies that the BALANCE at any given time is the sum of an initial value INITIAL --  BALANCE[CLIENT] and the integral of the difference between MONEY --  IN[CLIENT] and MONEY --  OUT[CLIENT] between some initial time and the given time. As before, the entry after the first tilde represents the dimensions (dollars), and the entry after the second tilde is a comment explaining the meaning of BALANCE[CLIENT]. Note that the effect variable for this entry is BALANCE[CLIENT], while the cause variables are MONEY --  IN[CLIENT], MONEY --  OUT[CLIENT] and INITIAL --  BALANCE[CLIENT]. Again, the vertical line indicates the end of the entry for BALANCE[CLIENT]. 
     The next entry defines a relationship between the variable MONEY --  IN[CLIENT] and the variables INTEREST[CLIENT] and DEPOSITS[CLIENT]. The entry indicates that MONEY --  IN has the dimension dollars/week and explains that MONEY --  IN is a rate. 
     The next entry defines MONEY --  OUT as the sum of the variables WITHDRAWALS and FEES. 
     Unlike the first three entries, each of which actually represents two equations, the next entry represents only one equation; it uses as a subscript the constant MARY rather than the variable CLIENT. The fifth entry similarly represents only one equation. In accordance with the syntax of the model-writing language, the dimensions and comments for two variables that differ only in subscripts can be written in common, even though their equations are entered separately, and this is the result of following the first equation simply with two tildes and a vertical line but following the second equation with a dimension and a comment. 
     The sixth entry, the one for INTEREST[CLIENT], is self-explanatory. The seventh entry describes a two-level interest rate. It states that INTEREST --  RATE[CLIENT] takes on the value of LOW --  INTEREST --  RATE/100 if the BALANCE[CLIENT] is less than $1,500 and is equal to HIGH --  INTEREST --  RATE/100 otherwise. 
     Although the foregoing equations do not mention time explicitly as an independent variable, reflection reveals that the first equation invokes it implicitly, and many of the variables consequently are functions of time. Specifically, since the first equation invokes the function INTEG, which represents evaluation of a definite integral whose upper limit depends on time, BALANCE[CLIENT] is a function of time. Since the variable FEES[CLIENT] depends on BALANCE[CLIENT], it also is time-dependent, as are INTEREST --  RATE[CLIENT], INTEREST[CLIENT], MONEY --  OUT[CLIENT], and MONEY --  IN[CLIENT]. 
     The purpose of the simulation program is to evaluate the various variables at successive values of the independent variable, which is typically assumed to be time. Accordingly, the simulation language will typically have variables reserved for this function, and the user may give them values in the following manner: 
     
         ______________________________________                                    
FINAL.sub.-- TIME = 1995                                                  
.sup.˜ year                                                         
.sup.˜ The final time for the simulation.                           
|                                                                
INITIAL.sub.-- TIME = 1990                                                
.sup.˜ year                                                         
.sup.˜ The initial time for the simulation.                         
|                                                                
TIME.sub.-- STEP = 1/52                                                   
.sup.˜ year                                                         
.sup.˜ The time step for the simulation is one week.                
|                                                                
SAVEPER = TIME.sub.-- STEP                                                
.sup.˜ year                                                         
.sup.˜ The frequency with which data is stored.                     
|                                                                
______________________________________                                    
 
    
     The first two entries tell when, in simulated time, the simulation is to start and stop. The third entry specifies that the simulation is to make successive calculations in steps of one week of simulated time. The user may not be interested in the results of each week; he may instead be interested only in the results of each year. In such a situation, the simulation would not need to retain the weekly results for display purposes, and it could discard them as soon as they are no longer needed for subsequent calculations. In the illustrated example, however, the user wants to see all of the results, and the fourth entry, which specifies that the save period is equal to the time step, gives this information to the simulation routine. 
     With this simulation program entered, the user commands the computer to run the simulation program 24, which thereby produces results 26. The memory containing the simulation results can be thought of as being organized into data groups, one for each variable, containing the simulation results as well as other information related to the associated variables, such as its cause and effect lists, the equations in which they are the effects, comments regarding the equations, and so forth. 
     In one embodiment of the invention, the presentation module 28 then presents the user a display of the type shown in FIG. 2. A number of the items of the display are not relevant to the present invention, and they will not be described here. But a major part of the display is a &#34;toolbox&#34; area 30, which contains a number of tool symbols of the type that can be employed in the present invention. The tool symbols typically take the forms of icons, by which the user can choose one of a number of data-group operations. 
     Above the toolbox area 30 is a &#34;workbench&#34; area 31, which includes a number of &#34;buttons&#34; 32-35. These buttons contain the legends &#34;variable,&#34; &#34;subscripts,&#34; &#34;runs&#34;, and &#34;globals&#34;. The user may &#34;click on&#34; the &#34;variable&#34; button 32 by using a mouse or other input device to move a display cursor over it and then pushing a button on the input device. This indicates that the user wishes to place a variable in the workbench, and a window 36 pops up in response. The part of the window relevant to the present invention is a list 37 of the variables in the simulation that he has entered. For the purposes of illustration, we assume that the user then moves the cursor over the &#34;balance&#34; entry 38 in the list and, say, double clicks on it. As a result, that variable appears, as shown, in the workbench. 
     As FIG. 2 shows, the variable BALANCE is shown with its variable subscript name, namely, CLIENT. The user could then click on the &#34;subscripts&#34; button 33 to enter one of the individual values for CLIENT, namely, MARY or JOHN, but we will assume for the purposes of the present explanation that he does not. Instead, he proceeds directly to choosing a data-group operation by clicking on one of the tool symbols in the toolbox 30. The chosen data-group operation is then performed on the data groups represented by BALANCE[CLIENT], i.e., by the name displayed in the workbench area 31. 
     We refer to the identifiers of the data groups by the term names and to the identifiers of the data-group operations by the term symbols. This nomenclature was chosen for its intuitive appeal, since the identifiers of the operations are typically in the forms of icons, while those of the data groups are typically alphanumeric. But the tool symbols can just as well take other forms, such as groups of alphanumeric characters, while the names of the data groups, although almost always in the forms of strings of alphanumeric characteristics, can just as well be icons. 
     One of the tool symbols that the user may designate is icon 40, which represents the operation of graphing as functions of time the values that the simulation has calculated for the variable whose name is displayed in the workbench. If the simulation has been run more than once, the user can use the &#34;runs&#34; button to specify the run whose results he wants to graph. Since the user has not specified a particular subscript, the name in the workbench actually represents two variables, both of which the presentation module 28 graphs in response to designation of the graphing icon 40. The particular icon shown represents a strip graph, i.e., a graph in which different variables are plotted on different axes, but a typical embodiment of the present invention will also provide a data-group operation in which the several graphed variables are plotted on common axes. FIG. 3 represents part of the resultant display, namely, the graph of the values of BALANCE[MARY] as a function of time. BALANCE[JOHN] would also be graphed. 
     The data-group operations represented by tool symbols 41 and 42 are similar to the one represented by tool symbol 40; they all represent graphing data. Tool symbol 41 represents graphing the proximate cause variables of the variable whose name is in the workbench area 31, and symbol 42 represents graphing its proximate effect variables. 
     For instance, clicking on tool symbol 41 would result in the display depicted in FIG. 4, namely, a plot of BALANCE[MARY] as well as of its three proximate causes MONEY --  IN[MARY], MONEY --  OUT[MARY], and INITIAL --  BALANCE[MARY]. The first two of these cause variables are shown graphically, while INITIAL --  BALANCE[MARY], which is a constant, is merely displayed numerically. The display would similarly show BALANCE[JOHN] as well as its causes. 
     Tool symbols 43, 44, and 45 represent operations that parallel those represented by symbols 40, 41, and 42, with the exception that the operations that they represent present the data in tabular, rather than graphical, form. 
     Tool symbols 46 and 47 represent data-group operations that parallel those of the operations represented by tool symbols 41 and 42 in that they call for presentation of causes and effects, respectively. Rather than causing the values to be displayed, however, they merely cause the names of the causes and effects to be displayed, and they show not only proximate causes but also other causes to a level three deep in the causal chain. 
     To obtain further insight into the causes of BALANCE[CLIENT], for example, the user may click on tool symbol 46. The result is the display shown in FIG. 5, which is a tree diagram of the causes of BALANCE[CLIENT]. This diagram lists not only INITIAL --  BALANCE, MONEY --  IN, and MONEY --  OUT, which are the proximate causes of BALANCE[CLIENT], but also variables on which those proximate causes depend. 
     The operation represented by tool symbol 46 is arranged to display only three levels of causation. Moreover, even if the BALANCE entries at the left side of the diagram were not disposed three levels deep in the causal chain, cause variables for them would not additionally be shown, since they are the same as those for the same, ultimate effect variable BALANCE at the right, and further display of the causes of these variables would thus be redundant. The fact that there is such a causal loop is indicated by the angle brackets in the drawing. 
     In order to identify any such loops, the user may click on tool symbol 48, which requests a list of loops. The result would be the display of FIG. 6. The display of FIG. 6 lists loops in tabular form and shows not only the two loops that are evident from the display of FIG. 5 but also a third loop, which would have been evident if the tree display of FIG. 5 had been extended by one level. 
     The causes of BALANCE can be shown in yet another way by clicking on tool symbol 49, which gives a causation tree in tabular form, as FIG. 7 shows. 
     Tool symbols 50, 51, and 52 represent further graphing operations, which will not be separately illustrated. Tool symbol 50 represents preparation of a Gantt chart. Clicking on that tool symbol causes both of the BALANCE[CLIENT] variables to be displayed in a Gantt chart, in which the bars that represent their presence would start and stop at the points in time at which the values of those variables pass through predetermined thresholds. Clicking on tool symbols 51 and 52 would cause display of vertical and horizontal bar charts that would depict the values of the two variables BALANCE[MARY] and BALANCE[JOHN] at a predetermined point in time. To set the time limits on the displays, the thresholds for the Gantt charts, and other display parameters, the user clicks on the &#34;globals&#34; button and is provided with displays that enable him to perform such operations. 
     Clicking on tool symbol 53 would result in computation and display of certain basic statistics, such as mean, deviation, etc. 
     The user may also want to review the entries that he made for the variable in creating the model. For this purpose, he may click on tool symbol 54, which would cause display of the entries that he made to define the variable whose name is on the workbench. Such an operation may simply show the equation, or it may additionally show the entered units and any comments that the user entered. At this point, the user may have learned something through his review of the data and may want to record the information for further reference by adding it to the comment that he initially entered. For this purpose, he can click on tool symbol 55, which would enable him to edit the entry for that variable. 
     A final tool symbol is symbol 59. This symbol represents the operation of performing a dimensional analysis on the equation in which the variable in the workbench is the effect. That is, clicking on this symbol causes this system to determine whether the units written in the equation are consistent and generates a display that tells the user the results of that determination. 
     For the sake of explanation, the model illustrated above is very simple and can readily be understood without using the more-sophisticated features of a simulation program. But it is not uncommon for a simulation to involve thousands of equations and tens of thousands of variables. It is in such simulations that the ease of presentation afforded by the present invention yields the greatest advantage. This is particularly true when the invention is embodied in a system that is capable of data-group operations like the cause and effect operations described above, which place on the display the names of the data groups associated with the cause or effect variables of the variable whose name is currently &#34;on the workbench.&#34; 
     In investigating a particular variable, for example, a user can display a causation tree by simply clicking on tool symbol 46 or 49, as was described above. When the tree is displayed, he can then look at a particular cause variable by merely clicking twice on its displayed name and once on the appropriate tool symbol, which may be the graph symbol 34. After seeing the behavior of that particular variable, the user may want to find out what else that variable affects, and he may therefore click on the effect-tree symbol 47. In this way, the user moves in a very natural way through the chains of causation in the model. 
     Because of the natural way in which he is able to work, the user can concentrate more on the model and less on the process of interacting with the computer than he could with a less natural presentation scheme. The use of the present invention thus greatly facilitates the user&#39;s investigation of the behavior of a computer model, and it thus constitutes a significant advance in the art.