Web > Charts > Chart Type Walkthroughs > Radial

Stacked Rose of Volume by Region and Desk

Known issues

Some chart features have known issues in the current release. See Known issues.

This walkthrough draws one wedge per region, stacked by desk, answering "Which regions trade the most, and on which desks?"

Prerequisites

• Editor mode: click once on the screen, then press Ctrl+d. The AMIDB Shell Tool and the gallery are used as in the quickstart.
• Data: the example data that stage 1 creates. To use a table of your own instead, see With your own data.

1. Create the example data

The chart reads a table in the Center, so create the table first.

1. Select Dashboard -> AMIDB Shell Tool....

2. Run:

   CREATE PUBLIC TABLE ChartDemoRegional (Region String, Desk String, Qty Long);
   INSERT INTO ChartDemoRegional VALUES ("Americas", "Equities", 40), ("Americas", "FX", 25), ("EMEA", "Equities", 30), ("EMEA", "FX", 35),
    ("APAC", "Equities", 20), ("APAC", "FX", 45), ("LatAm", "Equities", 15), ("LatAm", "FX", 10);
   SELECT * FROM ChartDemoRegional;
   

3. Check that the lower pane shows the 8 rows.

2. Create the chart

The gallery creates a datamodel that reads the table, then places the chart.

1. Select Windows -> New Window, then the edit button on Blank1, then "Create Table / Visualization / Form".
2. Select "AMI (__AMI)", then "Next >>".
3. Select the "USER" tile ChartDemoRegional, then "Next >>".
4. Select "Test (alt+enter)", then "Next >>".
5. Select the "Radial" tab, then the "Stacked Rose" tile.

6. Set the fields below the tiles:

   Field	Value
   "Wedge:"	Region
   "Stack by:"	Desk
   "Value:"	Qty

7. Select "Finish".

8. Check that the window shows 4 wedges labeled APAC, Americas, EMEA, and LatAm, LatAm being the shortest.

Result

4 wedges, one per region, each as long as its 2 desks' volumes together: Americas, APAC, and EMEA 65, LatAm 25. Each wedge is one color, so its 2 desks cannot be told apart on the chart.

The chart's own PNG export, from AmiScript toImagePng; see Chart type walkthroughs.

To check without looking, read the render stats: session.getDevTools().getAllRenderStats() in the AMIDB Shell Tool, with "Run on this web session" selected (see Running a script), or web_debug op=panelRenderStats over MCP. The "Rose" layer reports Rows 8, "4 groups", and an empty Problem.

With your own data

The chart needs one row per wedge and stack: a text column for "Wedge:", a text column for "Stack by:", and a number for "Value:". In stage 2, select the "USER" tile of your table in place of ChartDemoRegional, and map your columns to the fields in stage 2's field table. Stage 2's check quotes the example data; on yours, check the same features against your own values. To filter rows, or to total raw rows first, see Using your own data.

Over MCP

An agent builds the same chart from the same table. Connecting an agent is covered in the AI section; the tools are on Building charts over MCP.

1. Create the datamodel with web_execute op=importDatamodel and this dmJson, then run it once with op=initDatamodelSchema and dmName ChartDemoRegional:

   {"id": "ChartDemoRegional", "queryMode": "startup", "callbacks": [{"name": "onProcess", "amiscript": ["{ CREATE TABLE ChartDemoRegional AS USE ds=\"AMI\" EXECUTE SELECT * FROM ChartDemoRegional; }"]}]}
   

2. Create the chart:

   {"windowName": "ChartDemoRose", "templateKey": "tplRose", "datamodelId": "ChartDemoRegional", "dmTable": "ChartDemoRegional", "title": "ChartDemoRose", "bindings": "{\"CAT\": \"Region\", \"SER\": \"Desk\", \"VAL\": \"Qty\"}"}
   

3. Run the datamodel again with web_execute op=executeDatamodel, dmName ChartDemoRegional. A chart created over MCP can stay empty until its datamodel runs again, with its axes at 0-100.

4. Confirm that every layer reports the rows above and an empty Problem: run web_debug op=panelRenderStats.

The call is web_create_chart_from_template.

Removing the example

Remove the chart, then its datamodel, then the table, so that the next walkthrough can reuse the names:

1. Close the chart's window with its close button, and select "Delete" when asked whether to delete the panel.
2. Select Dashboard -> Data Modeler..., expand "Datamodels", right-click the chart's datamodel, ChartDemoRegional, and select "Delete Datamodel", then "Yes". If that name was taken when stage 2 ran, the gallery added a number to it, as in ChartDemoRegional1.
3. Run DROP TABLE ChartDemoRegional; in the AMIDB Shell Tool.
4. Check that SELECT * FROM ChartDemoRegional; reports Unknown table: ChartDemoRegional.

Over MCP, delete the chart with web_danger op=deletePanel, then the datamodel with op=deleteDatamodel, dmName ChartDemoRegional, and drop the table as in step 3. deleteDatamodel refuses a datamodel that has been committed; delete that one in the Data Modeler as in step 2. See Removing an agent's chart.