Documentation · Data
Radar chart
Name three or more spokes, then one series per polygon. Every spoke shares one scale, so give the readings the same range.
When to use it
Compare a few things across the same set of criteria: model evaluations, skill profiles or product scorecards.
Keep to three to eight spokes and two or three series, all on one scale. A radar chart's area depends on spoke order, so do not read area as a total.
Working example
Copy this complete example into the Source tab, then press Generate. Change its labels or values to make your first version.
radar "Model comparison" {
categories Accuracy Speed Robustness Interpretability Efficiency
series "Model A" 8 6 7 5 6
series "Model B" 6 9 5 7 8
range 0 10
}Syntax reference
The same reference used by the editor and AI briefing. Syntax is notation-specific; use the keywords listed here.
Chart
| Syntax | Meaning |
|---|---|
radar "Title" { | open a radar chart |
Readings
| Syntax | Meaning |
|---|---|
categories Speed Cost Safety | name the spokes, three or more |
series "Model A" 8 6 7 | one polygon across those spokes |
series "B" "#eb6834" 6 9 5 | a polygon in a colour of its own |
Wheel
| Syntax | Meaning |
|---|---|
area on | fill each polygon |
markers on | a dot at every reading |
range 0 10 | pin where the spokes start and end |
Look
| Syntax | Meaning |
|---|---|
colors colorful | auto, single, colorful, warm, cool, ink |
colors "#2a78d6" | one colour, pinned |
style framed | plain, ruled, framed, bold |
legend bottom | auto, none, right, bottom, top |
values on | write the number on every mark |
size 520 340 | how big the chart is drawn |
# comment | line comment (also //) |
Language rules
- The file is one radar "Title" { ... } block. Nothing may sit outside it.
- Name the spokes with categories, three or more, then write each thing compared as series "Name" 8 6 7, one value per spoke.
- Every spoke runs on one scale, so the readings should share a unit; range 0 10 pins it.
- Settings are written as name value, in any order.
- Do not invent settings. Every one the language has is listed above.
Edit on the canvas
- Drag a dot along its spoke to change that reading.
- Choose filled or outlined polygons and pin the scale in the chart panel.
Generate replaces the drawing from source. Save before generating again if you want to preserve manual finishing touches.
Read Saving & exportingWrite it with an assistant
Tingraph AI already knows this notation. For another assistant, copy the tutorial below, describe your diagram under MY DIAGRAM, then paste the returned source into the editor. This prompt includes every syntax row, rule and working example above.
Read the complete prompt
You are writing Tingraph source. Tingraph is a small text language that draws a radar chart. Answer with Tingraph source only.
SYNTAX
Chart
radar "Title" { open a radar chart
Readings
categories Speed Cost Safety name the spokes, three or more
series "Model A" 8 6 7 one polygon across those spokes
series "B" "#eb6834" 6 9 5 a polygon in a colour of its own
Wheel
area on fill each polygon
markers on a dot at every reading
range 0 10 pin where the spokes start and end
Look
colors colorful auto, single, colorful, warm, cool, ink
colors "#2a78d6" one colour, pinned
style framed plain, ruled, framed, bold
legend bottom auto, none, right, bottom, top
values on write the number on every mark
size 520 340 how big the chart is drawn
# comment line comment (also //)
RULES
- The file is one `radar "Title" { ... }` block. Nothing may sit outside it.
- Name the spokes with `categories`, three or more, then write each thing compared as `series "Name" 8 6 7`, one value per spoke.
- Every spoke runs on one scale, so the readings should share a unit; `range 0 10` pins it.
- Settings are written as `name value`, in any order.
- Do not invent settings. Every one the language has is listed above.
WORKED EXAMPLE
radar "Model comparison" {
categories Accuracy Speed Robustness Interpretability Efficiency
series "Model A" 8 6 7 5 6
series "Model B" 6 9 5 7 8
range 0 10
}
OUTPUT
- Reply with one fenced code block and nothing else.
- The block starts with `radar "…" {` and ends with `}`.
- Do not invent keywords: use only the ones listed above.
- Keep labels short enough to read inside a box, and keep every ID unique.
MY DIAGRAM
Describe what you want here, then send this message.Something unclear? Contact support or read the Privacy Policy.