Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make number of examples per call consistent? #18

Open
scottveirs opened this issue Mar 13, 2023 · 3 comments
Open

Make number of examples per call consistent? #18

scottveirs opened this issue Mar 13, 2023 · 3 comments
Assignees
Labels
catalog-content enhancement New feature or request

Comments

@scottveirs
Copy link
Member

Currently the number of examples provided for each of the SRKW calls varies a lot: from

2 S08s and S14s and S42s

to

13 S19s

In the long run, it might be nice to aim for a consistent number across all signal types for a catalogued repertoire. For example, if there were 4 "ideal" examples of each type, then a future UI could offer them in a 4-column grid, so that one's eye could more quickly scan down the grid for the next call type or a specific call type of interest...

@scottveirs
Copy link
Member Author

Correction: the smallest number of samples is --

1 S08ii

whereas there are 3 S08i examples.

@JKBF
Copy link
Collaborator

JKBF commented Mar 31, 2023

Thanks for the suggestion. Some call categories are far more variable than others, hence the need for some call types to have multiple examples to fully illustrate the range of variability. Simple call types like S05 and S04 don't need more than two or three. I agree that 13 examples for S19 is excessive however -- I'll delete some that are redundant. And I'll try to find a couple more S08ii!

@scottveirs
Copy link
Member Author

scottveirs commented Apr 12, 2023

I'll defer to @git-steb about how realistic this is to implement, but a possible alternative to deleting them, John, might be to ask for the catalogue software to set the maximum number of examples to display per call type. It could default to some number that you specify -- e.g. 5 or 8 -- so that the variability of calls like S19 is captured adequately.

However, if the UI allowed a user could change the threshold, perhaps they'd decide to decrease it in order to view only the "top 3" examples. This could work especially well if the example audio files were ordered in the audio repository from most commonly heard to most rarely heard.

Or maybe the user would like a really simplified catalogue with only a single example of the most common variation of a call. This might look closer to what Val and his Colorado College students implemented in the first online version of your SRKW catalog we shared with the Orcasound listening community ~20 years ago:

Screenshot 2023-04-11 at 11 45 45 PM

Alternatively, a different user might be trying to match a tricky/rare version of a single call. In that use case, they might want to increase the threshold to display and compare 10s or even (someday) 100s of examples of a single call type. This might eventually result in a really dense grid of examples, akin to the Google Experiment that visualizes a wide range of sounds from bird song:

Screenshot 2023-04-11 at 11 50 23 PM

In any case, don't delete those files! Every hard-won decision you've made about placing a call within one of your types is valuable, IMHO. Even if it's not used in the catalog, I'm sure there will be data scientists eager to use it as a labeled signal.

@VWJF VWJF added enhancement New feature or request catalog-content labels May 11, 2023
@scottveirs scottveirs self-assigned this Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
catalog-content enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants