You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure it is an issue, more in the grey area of unexpected behaviour.
As the title states, when I'm using the function predict_species_at_location_and_time I get a dictionary, while its keys do not include anthropogenic sound labels.
A simple workaround is to add them manually from the labels text file (as I did).
Although, in my humble opinion, it is not an expected behaviour, since human generated sounds are expected to be found in every location a recorder is placed.
It got there by someone or a someones' made vessel, I guess it is also maintained periodically... well you got the point.
I think at least it should be mentioned in the documentation (unless I missed that point, apologies in advance).
The text was updated successfully, but these errors were encountered:
I'm not sure it is an issue, more in the grey area of unexpected behaviour.
As the title states, when I'm using the function
predict_species_at_location_and_time
I get a dictionary, while its keys do not include anthropogenic sound labels.A simple workaround is to add them manually from the labels text file (as I did).
Although, in my humble opinion, it is not an expected behaviour, since human generated sounds are expected to be found in every location a recorder is placed.
It got there by someone or a someones' made vessel, I guess it is also maintained periodically... well you got the point.
I think at least it should be mentioned in the documentation (unless I missed that point, apologies in advance).
The text was updated successfully, but these errors were encountered: