We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's usually useful to group recordings by site/location.
Most arrangements of audio files places the audio recordings from a deployment into their own folder.
Idea 1: Return the parent folder name for files (2 levels up for FL/OAD files that are split into day folders) as an estimated site name.
Idea 2: cluster recordings on two dimensions
to estimate a deployment name. E.g. Samford North 2023, Samford North 2024, Samford West 2023.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It's usually useful to group recordings by site/location.
Most arrangements of audio files places the audio recordings from a deployment into their own folder.
Idea 1: Return the parent folder name for files (2 levels up for FL/OAD files that are split into day folders) as an estimated site name.
Idea 2: cluster recordings on two dimensions
to estimate a deployment name. E.g. Samford North 2023, Samford North 2024, Samford West 2023.
The text was updated successfully, but these errors were encountered: