> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/chord-diagram/data-structure.md). # Data structure ### Balanced matrix Creating a chord diagram with a balanced matrix involves using a square matrix where the rows and columns represent the same categories, and the values indicate the relationships or flows between them. A balanced matrix means that the sum of the rows equals the sum of the columns for each category, often used to visualize symmetric relationships or flows in a system. | | A | B | C | | - | - | - | - | | A | 0 | 5 | 5 | | B | 5 | 0 | 5 | | C | 5 | 5 | 0 | ### Unbalanced matrix A chord diagram with an unbalanced matrix represents data where the sum of the rows does not necessarily equal the sum of the columns. This is common in many real-world scenarios where the flow or relationship between entities is not symmetric. | | A | B | C | | - | -- | -- | -- | | A | 0 | 30 | 10 | | B | 20 | 0 | 40 | | C | 50 | 10 | 0 | | D | 10 | 30 | 0 | ## Interpretation * **Thickness of chords**: The width of a chord segment for a category indicates the magnitude of flow from or to that category. If a chord is thicker on the left side where it connects to A, it shows that A is contributing more to another entity than it is receiving. * **Disparities**: Any visible disparity in the thickness of the chord at either end highlights the imbalance in the relationship. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.infotopics.com/showmemore/features/chord-diagram/data-structure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.