[Tracking] Support for graphs (node-link diagrams) #7897
Labels
feat-graph-view
Everything related to the graph view
🎄 tracking issue
issue that tracks a bunch of subissues
This will touch various areas of Rerun so we will split the work up over multiple PRs. This PR is a living document and will be updated to reflect the current status of the implementation.
Must-haves for the initial release
Corresponding PR: #7500
gen_common_index.py
unused
lint warnings for things that we need in the futureGraphType
datatype::StringPair
and switchGraphNode
toUtf8
Utf8Pair
VisualBounds
in Viewer Propertiesentity_offset_x
to C++ and Python examplesFuture work
We will tackle the following things after #7500 lands.
Data Model
<entity_path>#<node_id>
convention. (Allow linking ofGraphNodes
across different entities #8162)chunk_id_removed.is_some()
#7992).Graph Layout & Viewer
We decided to start with implementing force-based layouts, because they support a wide variety of use cases and allow dynamic/temporal graphs out of the box.
positions: Position2D
component (closed by Implement graph components and archetypes #7500)fdg
,layout-rs
,graphviz-rust
). All of them have some shortcoming for our use cases.d3-force
. (⌛ Ongoing)d3-quadtree
to enable Barnes-Hut approximation 🏎️PositionX
andPositionY
forceCollide
forceManyBody
forceExamples & SDK
ProjectDirs
to pull in datasets for examples (social
graph; Observable)The text was updated successfully, but these errors were encountered: