Describe the bug
The argument --merge_consecutive is not working as expected in the CLI. I intend to combine all consecutive detections. According to the documentation I should set --merge_consecutive to 'None', but the argument only expects int values. Integer values 0 or 1 behave as expected, i.e. consecutive detections are not merged (see Example 1). Other integer values e.g. 3 are supposed to set the maximum number of consecutive detections to merge. However, when I use --merge_consecutive 3 only entries with 3 consecutive detections are merged. If there are only 2 consecutive detections they remain separate entries in the result table (see Example 2).
To Reproduce
Steps to reproduce the behavior (CLI):
Example 1:
python -m birdnet_analyzer.analyze E:\test_in -o E:\test_out --slist E:\species_labels.txt --min_conf 0.1 --rtype 'csv' --merge_consecutive 'None' --split_tables
Example 2:
python -m birdnet_analyzer.analyze E:\test_in -o E:\test_out --slist E:\species_labels.txt --min_conf 0.1 --rtype 'csv' --merge_consecutive 3 --split_tables
Expected behavior
Example 1:
I imagined --merge_consecutive 3 to work as a max value only, instead it works and min AND max
Example 2:
--merge_consecutive 'None' should merge all concsecutive detections independet of any min or max values, but it is not accepted as an argument setting.
Screenshots
Example 1:
Example2:
Emberiza citrinella had 6 consecutive detecions, so it is now 2 entries of 9 seconds each. Cuculus canorus had only 2 consecutive detections wich are still 2 entries of 3 seconds each.
Desktop (please complete the following information):
- OS: Win11Pro
- Version 25H2
Additional context
--split_tables still ignores output folder argument as described in issue #916
Describe the bug
The argument --merge_consecutive is not working as expected in the CLI. I intend to combine all consecutive detections. According to the documentation I should set --merge_consecutive to 'None', but the argument only expects int values. Integer values 0 or 1 behave as expected, i.e. consecutive detections are not merged (see Example 1). Other integer values e.g. 3 are supposed to set the maximum number of consecutive detections to merge. However, when I use --merge_consecutive 3 only entries with 3 consecutive detections are merged. If there are only 2 consecutive detections they remain separate entries in the result table (see Example 2).
To Reproduce
Steps to reproduce the behavior (CLI):
Example 1:
python -m birdnet_analyzer.analyze E:\test_in -o E:\test_out --slist E:\species_labels.txt --min_conf 0.1 --rtype 'csv' --merge_consecutive 'None' --split_tables
Example 2:
python -m birdnet_analyzer.analyze E:\test_in -o E:\test_out --slist E:\species_labels.txt --min_conf 0.1 --rtype 'csv' --merge_consecutive 3 --split_tables
Expected behavior
Example 1:
I imagined --merge_consecutive 3 to work as a max value only, instead it works and min AND max
Example 2:
--merge_consecutive 'None' should merge all concsecutive detections independet of any min or max values, but it is not accepted as an argument setting.
Screenshots
Example 1:
Example2:
Emberiza citrinella had 6 consecutive detecions, so it is now 2 entries of 9 seconds each. Cuculus canorus had only 2 consecutive detections wich are still 2 entries of 3 seconds each.
Desktop (please complete the following information):
Additional context
--split_tables still ignores output folder argument as described in issue #916