Open Nirosha201 opened 5 years ago
Good question.
For detection performance, it doesn't matter that much because the wavelet packet is generated once no matter how many species or call types are requested. But currently there is no way to "select" only one call type from existing annotations - so it's not possible to exclude other call types from review / xls output or anything. Should think how to implement this in a consistent way.
I think that this can be a good idea. I don't know if could be reasonable to generate a more-pork filter and then separate call filters or if it is better to have the ability to select the call from the main filter.
Do we need to have the option to choose the entire filter or specific sub-filter within that filter, particularly in batch processing? My concern is some users might want to focus only on one call type of the species, in those cases there is no point of running the entire filter. e.g. Morepork filter got few subfilters and someone only need to extract more-pork cal type.