calebkaiser

calebkaiser OP t1_iwncxdj wrote

Someone on our team did bring this up a couple of weeks ago, but I have to admit, it was after we'd named the project Kangas.

Originally, Kangas was just the working name of the project (our research team's mascot is the kangaroo). When we finally decided to put our heads together and name the project something "official," we'd all grown a bit attached to Kangas and it stuck.

I do wish I could pass myself off as worldly enough for that reference though :)

7

calebkaiser OP t1_iwnci0b wrote

We're big admirers of FiftyOne. Kangas is similar in its approach to UI and some other aspects, but our focus is different. In particular, FiftyOne is really laser-focused on computer vision, whereas Kangas is a more general EDA tool that happens to have some CV features.

To give a more concrete example, Kangas handles all kinds of data, and we put a lot of work into autogenerating charts and aggregate statistics from your dataset regardless of the kind of data you log. Our immediate roadmap involves broadening this even further, adding more advanced support for video, audio, and more. But, we don't have as deep of a feature set specifically for computer vision as FiftyOne.

9