Pie Chart of Share by Symbol¶
Known issues
Some chart features have known issues in the current release. See Known issues.
This walkthrough draws each symbol's share of the total as a slice, answering "What share of the volume did each symbol take?"
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.
- Select Dashboard -> AMIDB Shell Tool....
-
Run:
-
Check that the lower pane shows the 5 rows.
2. Create the chart¶
The gallery creates a datamodel that reads the table, then places the chart.
- Select Windows -> New Window, then the edit button on
Blank1, then "Create Table / Visualization / Form". - Select "AMI (__AMI)", then "Next >>".
- Select the "USER" tile
ChartDemoTotals, then "Next >>". - Select "Test (alt+enter)", then "Next >>".
- Select the "Radial" tab, then the "Pie Chart" tile.
-
Set the fields below the tiles:
Field Value "Slice size:" Qty, as filled in.sum(Qty)draws every slice the same size, with no percentages"Slice label:" Symbol -
Select "Finish".
- Check that the window shows 5 slices, labeled with their symbols and percentages, the largest being JPM.
Result¶
5 slices: JPM about 41%, AAPL about 25%, IBM about 17%, MSFT about 12%, and NVDA about 4%.
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 layer reports Rows 5 and an empty Problem.
With your own data¶
The chart needs one row per slice: a text column for "Slice label:" and a number for "Slice size:". In stage 2, select the "USER" tile of your table in place of ChartDemoTotals, 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.
-
Create the datamodel with
web_executeop=importDatamodeland thisdmJson, then run it once withop=initDatamodelSchemaanddmNameChartDemoTotals: -
Create the chart:
-
Run the datamodel again with
web_executeop=executeDatamodel,dmNameChartDemoTotals. A chart created over MCP can stay empty until its datamodel runs again, with its axes at 0-100. - Confirm that every layer reports the rows above and an empty
Problem: runweb_debugop=panelRenderStats.
The call is web_create_chart.
Removing the example¶
Remove the chart, then its datamodel, then the table, so that the next walkthrough can reuse the names:
- Close the chart's window with its close button, and select "Delete" when asked whether to delete the panel.
- Select Dashboard -> Data Modeler..., expand "Datamodels", right-click the chart's datamodel,
ChartDemoTotals, and select "Delete Datamodel", then "Yes". If that name was taken when stage 2 ran, the gallery added a number to it, as inChartDemoTotals1. - Run
DROP TABLE ChartDemoTotals;in the AMIDB Shell Tool. - Check that
SELECT * FROM ChartDemoTotals;reportsUnknown table: ChartDemoTotals.
Over MCP, delete the chart with web_danger op=deletePanel, then the datamodel with op=deleteDatamodel, dmName ChartDemoTotals, 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.
