Cluster and then Embed: A Modular Approach for Visualization
This paper proposes a transparent, modular visualization framework that improves upon methods like t-SNE and UMAP by sequentially clustering data, embedding each cluster individually, and then aligning them to preserve both local structure and global geometry.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you have a giant, messy box of 3D LEGO sculptures. Some are tiny, intricate castles; others are sprawling, flat cities. Your goal is to take photos of all of them and lay them out on a flat 2D table so you can see how they relate to each other.
The problem? If you just squish the whole box onto the table at once, the flat cities get crushed, and the castles overlap into a giant, confusing blob. This is the "crowding problem" that plagues popular tools like t-SNE and UMAP. They are great at keeping the tiny details of each castle together, but they often distort the map, making distant castles look like they are right next to each other.
Enter the Cluster+Embed (C+E) approach, a new method proposed by Elizabeth Coda, Ery Arias-Castro, and Gal Mishne. Think of this method not as a single magic camera, but as a three-step assembly line that treats your data like a collection of distinct neighborhoods.
Step 1: The Neighborhood Sort
First, the method doesn't try to photograph the whole box at once. Instead, it acts like a super-organized librarian who sorts the LEGO sculptures into separate piles based on their shape. If you have a pile of castles and a pile of cities, they get separated into different bins. The authors note that you can use any sorting method you like (like the popular Leiden or DBSCAN algorithms), but the key is that you define the groups before you take the picture.
Step 2: The Individual Photos
Next, the method takes a photo of each pile individually. Because the librarian is only looking at one pile of castles at a time, they can arrange the castles perfectly to show their intricate details without worrying about the cities getting in the way. This step uses standard tools (like PCA or TriMap) to flatten just that one group. The result? A crystal-clear, high-quality photo of the castles, and a separate, equally clear photo of the cities.
Step 3: The Global Map
Here is the clever part. Now you have a stack of perfect, separate photos. The final step is to tape these photos onto a giant wall to make one big map. But instead of just gluing them randomly, the method uses a "rigid transformation"—imagine picking up a whole photo of the castle pile and sliding it, rotating it, or flipping it, but never stretching or squishing the photo itself.
The goal is to position these piles so that the distance between the "castle pile" and the "city pile" on the wall matches the distance they had in the original box. To solve the crowding problem (where there isn't enough room on the wall for everything), the method introduces a "scaling knob" (called ). If the piles are too close and might overlap, the authors suggest turning this knob to gently push the piles apart, creating just enough space for everyone to be seen clearly without distorting the internal details of the photos.
What This Method Says "No" To
The authors are very clear about what they are fighting against. They argue against the idea that a single, all-in-one tool (like t-SNE or UMAP) can perfectly do two contradictory things at once: keep the tiny local details perfect and keep the global distances accurate. They show that while t-SNE is great at separating clusters, it often distorts the "map" so much that you can't trust the distances between the groups. They also explicitly rule out the idea that you can just force a hierarchical tree onto a map without a structured process; their method is a deliberate, transparent three-step pipeline, not a black box.
How Sure Are They?
The authors don't claim this is a magic bullet that solves everything forever. Instead, they present strong evidence from simulations and real-world data.
- On Synthetic Data: They tested their method on a 10-dimensional Gaussian mixture model with 5,000 points. In these simulations, they showed that with a scaling factor of , their method avoided the overlap that plagued other methods, creating a ring of clusters that looked very similar to t-SNE but was achieved through a transparent, controllable process.
- On Real Data: They applied this to three real datasets:
- MNIST (Handwritten Digits): A dataset of 60,000 images. Here, C+E successfully separated the digits into groups (like fours and nines being close) and preserved the global structure better than t-SNE, which tended to space everything out equally.
- Human Brain Organoids: A dataset of 20,272 cells. The method revealed a clear "developmental trajectory" (a path of growth over time) that was visible in their map but was more "discrete" and less continuous in t-SNE and UMAP.
- Mouse Cortex: A dataset of 23,822 cells. Here, C+E revealed a "coarse-to-fine" structure (big groups breaking down into smaller ones) that other methods missed.
The authors admit there is a trade-off. While C+E is excellent at preserving global distances and local shapes, it sometimes struggles to match t-SNE's ability to keep the very nearest neighbors (kNN recall) perfect for small values of . They suggest this is because t-SNE has a mysterious way of breaking data into tiny patches that C+E doesn't replicate. However, they argue that for a visualization that is both transparent and faithful to the overall shape of the data, C+E is a highly competitive and much more understandable alternative.
In short, the paper suggests that by breaking the problem into "sort, flatten, then align," we can get a map that doesn't lie about where things are, even if it takes a few more steps to get there.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.