search

cmudig / falcon-vis

Cross-filter millions (or even billions) of data entries with no interaction delay
https://dig.cmu.edu/falcon-vis/
BSD 3-Clause "New" or "Revised" License
94 stars 1 forks source link

bring back 2D views #115

Open xnought opened 1 year ago

xnought commented 1 year ago

We only have 1D views right now because the code for 1D is quite complex with the additions of categorical data too. First simplify 1D, then add 2D.

Unemyr commented 1 year ago

Hi, would just like to check if there is any update or more concrete plans to add back the 2D view support? Thanks in advance!

xnought commented 1 year ago

No concrete plans at the moment or in the near future. My bad for not updating the original issue.

Unemyr commented 1 year ago

No worries - thank you for the quick reply! I may not be familiar enough with this library to make the appropriate amendments myself, but if I were to have a go at it, would it be possible to get some rough guidance/a few key points on where/what changes would likely need to be made? Cheers, Erik

xnought commented 1 year ago

I might check out https://uwdata.github.io/mosaic/ if you're using duckdb stuff. You can get the same logic, but the 2D stuff is already implemented.

For falconvis, The implementation will be reasonably complex. That's the whole reason I'm not implementing it right now.

But what I would personally do is pick the data source I plan to use (arrow, duckdb, or other) and change the db file to also include a way to compute the 2D falcon index given two dimensions. https://github.com/cmudig/falcon-vis/tree/main/falcon-vis/src/db

Then add a custom View2D class which fetches that index and can subsequently be used given a filter. https://github.com/cmudig/falcon-vis/blob/main/falcon-vis/src/falcon.ts

I wish it could be easier. I'll see what I can do in the next few weeks, but no promises.

Unemyr commented 12 months ago

Thank you - I would definately offer to help do some additional testing on the new version, in ways I could contribute!