Embed table or graph with ACP

Revision as of 23:25, 19 February 2016 by Bbecane (talk | contribs)


<< ACP

Analytica lets you create user interfaces for Analytica Cloud Player (ACP) that embed tables and graphs within a Diagram window. This lets users view and input tables and result tables and graphs all in a single user interface window -- unlike Analytica on the desktop in which each input table and result table or graph must be in its own window.

There are two ways to do this. The simplest is to resize a user input or output node in Analytica so that its tall enough to show the table or graph (at least 4 times taller than the default size). It may look a little odd in desktop Analytica, which just shows the Edit table, Calc, or Result button in the tall node. But, when you load the model into ACP, it will automatically show the edit table for an input node. For an output node, it will display the result as a table or graph (in whatever form it was last saved in Analytica).

A second way to embed tables and graphs in a diagram uses Frames. A Frame is a rectangular area (defined by a Text node) that will display the edit table for any input node you click, or a result table or graph for any output node you click. See below for details.

Frame node

The current way (i.e. ACP 3 and above) to embed tables or graphs in a parent diagram window is to designate one or more Frame nodes, each of which can show a table or graph. In ACP, when you click on any other node in the diagram -- be it a user input, output, or a standard variable node in an influence diagram -- ACP displays its corresponding table or graph in a Frame node. (Atomic values don't display in a frame node, if the variable has an output node - they display directly on the output node.} This turns out to be very convenient as a way to see any input table or result in its parent Diagram window.

Normally, you specify which nodes are Frame nodes by naming them in the CloudPlayerStyles attribute of the parent model or module, i.e. not of the text node itself. In this example, we specify TextNode1 as a Framenode in Module : M:

Module M
CloudPlayerStyles: Framenode: Textnode1
Framenode01.PNG


Framenode02.PNG


Framenode03.PNG


Framenode04.PNG



If there is more than one Frame, ACP will display the table or graph in the frame with the earliest previous table or graph. Here is how you specify two Frames in a Diagram: Module M CloudPlayerStyles: Framenode:Textnode1 & TextNode2

Each time you click on a node, it will show its table or graph in the Frame whose contents was displayed the longest ago. Thus, as you click on different nodes, it cycles through the Frames. In this way, you can see and compare edit tables or results from multiple nodes -- all in the same diagram window.

Alternatively, you can specify that you want specific nodes displayed in specific frames. In this example, let's say you have a diagram with two nodes with edit tables, Inputdata1 and Inputdata2. And you have two nodes which show graphical results, called Result1 and Result2. You might specify one frame node, Textnode1, for handling the two inputs for the two edit tables and another Frame node, TextNode2, for displaying the result graph one at a time. In this case, you specify which Framenode to use in the CloudPlayerStyles of each variable, rather than in CloudPlayerStyles of the parent module:

Variable Inputdata1
CloudPlayerStyles: FrameNode: TextNode1

Variable Inputdata2
CloudPlayerStyles: FrameNode: TextNode1

Variable Result1
CloudPlayerStyles: FrameNode: TextNode2

Variable Result2
CloudPlayerStyles: FrameNode: TextNode2


Example 3: Using two frame nodes, where one is a module level framenode

Suppose your diagram has two input tables and five output nodes to show results. In this case, you decide you want to use one frame to display the two inputs, and another frame for results. In this case, you could set the CloudPlayerStyles for the two input tables, and set a module level CloudPlayerStyles which will be used by any other node, in this case  output nodes.

Variable Inputdata1
CloudPlayerStyles: FrameNode: TextNode1

Variable Inputdata2
CloudPlayerStyles: FrameNode: TextNode1

Module M
CloudPlayerStyles: FrameNode: TextNode2

Since the output nodes do not have an CloudPlayerStyles specifying a frame, they use the frame specified in the module's CloudPlayerStyles.

What is displayed?

In general, ACP will resize the contents of a frame node to fit into the frame, but in some models you may need to adjust your frame nodes larger so they display the way you want them to, depending on factors such as the complexity of the displayed result and the font size.

Title, Units and description: Normally ACP shows the node's title and units (If any) in bold at the top of the frame, followed by its description (if any). But, if the Description contains more text than will fit in the top third of the frame, it shows only what will fit in the top third, with a scrollbar to see more.

When a Diagram first opens in ACP (and no node has been selected), each frame node shows its own title, and description (if any). This is a useful place to put an introductory explanation of this diagram and how to use it.

Font size: It uses the font style and size specified for the frame node with the title in bold -- initially the title and description specified for the frame, and then the title and description for the selected variable.

It should allow web links (as in other descriptions) to appear in the description text.

FrameOptions:

  • Show_title: Set Show_title: no to stop showing the Title and units of a selected variable.
  • Show_description: nn: Where nn is a number between 0 and 100, where it uses up to nn% of the vertical space available to show the description, showing vertical scroller if that isn't enough to show the entire description. Set nn = 0, if you don't want to show the description at all (and no scroller). Default if not mentioned, is one third, i.e. Show_description: 33
  • Show_Index_menus: yes By default the index menus for pivoting and slicing are not shown in frame nodes, since often the modeler has already chosen the pivot she wants to use. And because these menus take up valuable screen space. If you do want to allow users to be able to pivote or change the slice of the table or graph, then use this flag (it's easiest to do this with the ACP Styles Library).
  • Graph_only: Shows graph (even if model author last saved result as a table)
  • Table_only: Shows table (even if model author last saved result as a graph)
  • Graph_over_table: Show graph above table in the same Frame.
  • Table_over_graph: Table above graph in the same Frame.

Example, to have the result graph show over the result table, and to allow the description to use up to 50% of the frame node area you would specify the following:

Text Textnode1
CloudPlayerStyles: Show_description: 50 Graph_over_table

Side note, if the graph of a particular variable is not meaningful (e.g. the result is scalar or a list of labels) the result table will be presented instead of the graph regardless.

Tall input and output nodes

(Tall output nodes are supported in ACP 2 and ACP 3, tall input nodes are supported currently in ACP 2 - coming soon in ACP 3).

To show a table or graph embedded in a diagram in ACP, you simply make its user input node for an edit table -- or user output node for result table or graph -- tall: That is, over four times its default height. The default height of a user input or output node is 26 pixels -- if it uses the default 11-point font size. So, "tall" means more than 104 pixels -- more for a larger font.

ACP sizes a graph automatically to fit the frame (node size) you have specified. This usually works well if you make the frame large enough. If an edit table or result table is larger than the node size, it shows scroll bars so you can scroll to see all parts of the table.

ACP uses the table or graph format last used in the version of the model you saved in Desktop Analytica. So, if you want ACP to show a graph (not result table), you should view it that way -- and set any other table or graph options you want -- before you save the model. Similarly, for an Edit table, choose the pivot (which index is rows and which columns) before you save the model. ACP also uses the uncertainty view -- mid, mean, statistics, pdf, cdf, or sample -- that you last viewed in DTA. (For experts, you can find this information in the ValueState attribute for the original node.)

Example usage

Here's how the modeler creates the output node in DTA:

Setting up embedded graph in dta.png

Here's the result displayed on the diagram in ACP:

Embedded result graph in awp.png

CloudPlayerStyle flags in tall output nodes New to ACP3

These flags can be used in tall output nodes-same as described above in frame nodes section.

  • Show_title
  • Show_description: nn
  • Show_Index_menus: yes
  • Graph_only
  • Table_only
  • Graph_over_table
  • Table_over_graph

If you would like this tall input feature or a similar feature to use in your model in ACP 3, let us know, and we'll probably implement it for you. E.g. Email us at acp@lumina.com.

Text Area Input Node

In ACP 2, if you make an input node that contains a single (atomic) text value tall (in DTA), ACP will insert a multi-line text box. This lets users enter multi-line input -- e.g. from copying and pasting multiple lines of text. A standard single line text box will not support multiline text input.

If you would like this feature or a similar feature to use in your model in ACP 3, let us know, and we'll probably implement it for you. E.g. Email us at acp@lumina.com.

See Also


<< ACP

Comments


You are not allowed to post comments.