Skip to main content
SimilarExport ZIP
100%

Force-Directed Graph V9

✓ Published8🌍 Public
Sschneich
Last edited Sep 9, 2022
Created on Sep 9, 2022

A force-directed graph visualizes application integration links from CSV data, mapping applications as circles and their interfaces as connecting lines. The simulation uses `d3.forceSimulation` with `forceManyBody`, `forceLink`, `forceCenter`, and `forceCollide` to position nodes, while user interaction is enabled through `d3.drag`. SVG rendering displays labeled nodes and grey links, with text identifiers from the `applications.csv` file. The graph dynamically updates node and edge positions on each simulation tick, showing the complex network of inter-application data flows.

AI-generated description

Creating a force-directed graph, based on data of two csv-files.

Sources: - Scatter Plot: https://www.youtube.com/watch?v=xkBheRZTkaw&t=37528s

Text, Color, Drag: https://youtu.be/y7DxbW9nwmo?t=1696

Filter:

open issues:

  • count number of links -> change force (number of links > 1 -> push appart / number of links < 1 -> force together)
  • add arrows to links
  • change interf.csv (wrong source data for filters)
  • add filter options
MIT Licensed

Similar vizzes

Loading thumbnail…

Force-Directed Graph V7

A force-directed graph visualizes application interfaces from CSV data, mapping each application to a colored circle with its name in a text label. The simulation uses d3.forceSimulation with forceManyBody, forceLink, forceCenter, and forceCollide to position nodes, while links are drawn as lines between connected applications. The code parses nodes and links from CSV files, assigns colors from a palette, and supports drag interaction to reposition nodes, restarting the simulation on each drag.

Sschneich
93% match
Loading thumbnail…

Force-Directed Graph V8

A network of 40 application nodes connected by 130 links visualizes system integrations, with each node labeled and draggable. The graph uses `d3.forceSimulation` with `forceManyBody`, `forceLink`, `forceCenter`, and `forceCollide` to position nodes, while SVG circles, lines, and text render the structure. Data comes from two CSV files—`applications.csv` for node IDs and `interf.csv` for link sources and targets. Nodes can be dragged via `d3.drag`, which fixes their position during interaction.

Sschneich
93% match
Loading thumbnail…

Fork of Force-Directed Graph V9

This force-directed graph visualizes application integration connections, with nodes representing software systems and links indicating data interfaces. Using D3 v7's `forceSimulation` API with `forceManyBody`, `forceLink`, `forceCenter`, and `forceCollide`, the layout balances node repulsion against link attraction. Draggable circles use the `drag` interaction, while grey lines and labels update positions dynamically. The graph is rendered as SVG, with node data from `applications.csv` and edge definitions from `interf.csv` representing real-world system dependencies.

TTom Ellis
92% match
Loading thumbnail…

Force-Directed Graph V6

This example shows a force-directed graph that maps software applications as circles and their interfaces as connecting lines, with node positions determined by physics-based forces. The visualization uses d3.forceSimulation, d3.forceManyBody, d3.forceLink, and d3.forceCenter to calculate layout, while SVG circles and lines render the network. It loads node and link data from separate CSV files (applications.csv and interf.csv) using d3.csv, and updates node positions on each simulation tick. The drag functionality is imported via d3.drag, though it is not explicitly invoked in the visible code.

Sschneich
92% match
Loading thumbnail…

Fork of Force-Directed Graph V9 11

A force-directed graph visualizes system interfaces between applications, with nodes representing software and links showing data connections based on two CSV files. The graph uses `d3.forceSimulation` with forces for charge, link distance, center positioning, and collision avoidance, while `d3.drag` enables interactive node movement. Each circle and text label updates position during simulation ticks, and grey lines connect related applications. The implementation reads node and link data from CSV files, then renders the network using SVG elements with D3 v7.

AAbdouEnsaj
91% match
Loading thumbnail…

Fork of Force-Directed Graph V9

This force-directed graph visualizes the relationships between applications in a hospital information system, using node and link data loaded from two CSV files. Nodes represent applications and links represent data interfaces between them. The example uses `d3.forceSimulation` with `forceManyBody`, `forceLink`, `forceCenter`, and `forceCollide` to position nodes, while circles and lines are rendered in SVG. Dragging is enabled via `d3.drag`, and node labels and link data are drawn from the parsed CSV rows.

GGauppi
88% match
Loading thumbnail…

Force-Directed Graph IT Fork Test

This example visualizes IT infrastructure dependencies as an interactive force-directed graph, with applications as nodes and their interfaces as links. The graph is rendered as SVG circles and lines, with node labels displayed alongside each circle. The code uses `d3.forceSimulation` with `forceManyBody`, `forceLink`, `forceCenter`, and `forceCollide` to position elements, while `d3.drag` enables interactive node dragging. It loads node and link data from separate CSV files (`applications.csv` and `interf.csv`), with links defined by named source and target accessors.

VVonBrank
88% match
Loading thumbnail…

Graph Playground

A force-directed graph shows connections between software applications, with nodes representing applications and links representing interfaces between them. The visualization uses a d3.forceSimulation with forceManyBody, forceLink, forceCenter, and forceCollide to position nodes, while SVG circles and lines render the network. Data comes from two CSV files: applications.csv defines node properties (including a colorID) and interf.csv provides source-target pairs with descriptive names. Users can drag nodes to reposition them, and the simulation updates link positions dynamically. Node labels display application IDs, though the colorID column remains unused.

KKyle?
88% match