Problems with browser client features

[edmcman]

I'm trying to play with Atlas, and I'm having trouble with a lot of features (in the "bells and whistles" sense) on my dataset:

1. Filtering by "correct" property is strange.

I have a "correct" property that is a boolean. Since Atlas doesn't support booleans, I converted it to an integer. The behavior when filtering on this field is odd. If you move the upper range below 1, no points display, ever. If you move the lower range above 0, sometimes you get points, and sometimes the space is blank. There are points with correct=0 and correct=1 (at least, there should be -- there are before I uploaded them to Atlas).

2. Searching by "correct" property

No matter what I try to search for, nothing happens when I try to search. You can't tell from the video, but I'm hitting enter between all of these.

3. Only "Dirname" shows up as an option for coloring, but I added Filename and correct as colorable fields as well. Maybe correct can't be used because it's an integer? But Filename is a string.

Any help would be appreciated. This seems like a neat project.

[bmschmidt]

Thanks so much for these helpful comments. I'm reaching out to your academic e-mail, but also want to provide a couple solutions here for you and anyone else who hits these problems while we're working on improving Atlas's features and documentation:

1. For a boolean correct property, it may make more sense to upload it as a string either [True, False]; then you can color by it and soon will be able to filter in the legend. We'll look into the behavior of the filter bar in the two-number case.
2. For searching on 'correct'--currently search only works on text fields.
3. filename won't work as a colorable field if it has too many distinct values (Ideally there should be between 2 and a couple hundred or thousand unique values: if you have more, you might want to create a new field were the less common ones are lumped together as 'other'). It's possible that correct may show up if you click on the "Progressive" instead of "Unique" color strategy field.

I'll also note for bumping these in our own internal issue tracking:

1. We should support boolean input columns;
2. We need to address the issue of unsearchable fields appearing;
3. We should do the auto-lumping of categorical errors on our end and display better feedback when fields are dropped.
4. The Progressive/Unique distinction continues to be confusing.

[edmcman]

Thanks for the help!

Based on your feedback, I changed correct to a string field. This did allow me to color by it (yay).

But search still doesn't work even though it is a text field. It seems to result in a query to https://api-atlas.nomic.ai/v1/project/search/regex?query=True&field=correct&project_id=c54d8dd8-5701-4fae-ac56-2392872e052b&projection_id=ca56362d-424f-4704-af1c-5b5e5a94345e&tiles=%5B%220%2F0%2F0%22%5D&regex=false&ignore_case=true&word_breaks=true which returns error 500.

Here's a link to the new map: https://atlas.nomic.ai/map/13640c39-0b57-444a-bf22-e5f8df46cf82/c6ad80e5-d90a-46e8-a6a2-218a0fb9cd25

[KastanDay]

Hi @bmschmidt,

Do you support filtering on a timestamp or date object? What would be the proper data format for that column?
Much appreciated. We're using nomic in UIUC.chat