Bioacoustic Logger Accuracy Test
ISEF Category: Animal Sciences
Ready to Turn This Idea Into a Real Project?
This guide was put together with the help of AI research tools to give you a solid starting point. But a competitive science fair project lives in the details: refining your research question, fine-tuning your variables, analyzing your data, and presenting your findings like a seasoned scientist.
For next steps tailored to your interests, skill level, and timeline, work one-on-one with a MehtA+ mentor. Learn more about MehtA+ Science & Engineering Research Mentorship →
Subcategory: Other · Difficulty: Intermediate · Setup: School Lab · Time: 1 to 2 Months
The Hook
A cheap recorder can miss the same bird your ear catches in seconds. That matters when scientists need data from many sites, not just one perfect microphone. Your project asks a clear question, can an open-source bioacoustic logger stay close to commercial units on public audio? If it can, you have a useful design that other student teams can build too.
What Is It?
A bioacoustic logger is like a security camera for sound. It records animal calls, song, and background noise, then software tries to name the species. In this project, you are not only building the recorder. You are also checking whether its answers match a commercial logger on the same audio clips.
Open-source means the design is public, so you can change the parts and code. Low-cost means you are trying to keep the whole build under $50. Benchmarking means you give every system the same test set, then compare scores like accuracy, precision, and recall.
Why This Is a Good Topic
This topic works well because you can test it with public audio, so you do not need months of fieldwork just to get started. It connects to wildlife monitoring, habitat surveys, and conservation work, where cheaper tools could cover more sites. You can learn hardware design, audio cleaning, and basic machine learning while still keeping the project focused and measurable.
Research Questions
- How does microphone type affect species-ID accuracy on the same public audio clips?
- What is the effect of enclosure design on false detections caused by background noise?
- Does adding a noise filter before classification improve accuracy on crowded soundscapes?
- To what extent does sample clip length change the logger's top-1 species-ID accuracy?
- Which audio feature set gives the best match between the open-source logger and commercial loggers?
- How does habitat noise level change precision and recall for common species?
Basic Materials
- Raspberry Pi Zero 2 W or similar single-board computer.
- USB microphone or I2S MEMS microphone module.
- MicroSD card with adapter.
- Portable USB power bank.
- Breadboard and jumper wires.
- Cardboard, 3D-printed plastic, or weatherproof project box.
- Laptop with internet access and labeled public audio clips.
Advanced Materials
- Reference-grade microphone.
- Audio interface with phantom power.
- Acoustic calibrator.
- Commercial bioacoustic logger for side-by-side testing.
- Weatherproof field enclosure.
- Battery and power-management module.
Software & Tools
- Python: Cleans audio, runs classifiers, and scores predictions.
- Jupyter Notebook: Tracks results, plots confusion matrices, and compares test runs.
- Audacity: Lets you inspect clips, trim noise, and spot bad recordings.
- scikit-learn: Computes accuracy, precision, recall, and confusion matrices.
- BirdNET Analyzer: Tests species-ID performance on labeled bird audio.
Experiment Steps
- Define the exact species-ID task you will score, such as top-1 label, top-3 label, or species presence.
- Choose one public audio dataset and one commercial logger output set, then make sure both are tested on the same clips.
- Build a label ruleset for clean calls, mixed calls, and noisy clips so your comparisons stay fair.
- Plan a scoring table with accuracy, precision, recall, confusion matrices, and cost per correct ID.
- Design stress tests that change noise level, clip length, and species mix so you can see where each logger breaks first.
Common Pitfalls
- Comparing systems on different clip lengths, which can make the logger with more audio look better than it is.
- Mixing labels from different databases without normalizing species names, which creates fake mismatches.
- Calling a genus-level match correct when the test asks for species-level ID, which inflates accuracy.
- Letting training clips leak into the test set, which gives you a score that will not hold up on new audio.
- Testing only clean bird songs and ignoring noisy habitat clips, which hides the cases where low-cost hardware struggles.
What Makes This Competitive
A strong version goes beyond a simple accuracy check. You compare the open-source logger and commercial units on the same clips, then split the results by noise level, species similarity, and cost per correct ID. If you add confidence intervals or another statistical test, your results say more than "one score was higher." That kind of analysis shows real engineering judgment.
Project Variations
- Compare forest, wetland, and urban audio to see which habitat creates the most false IDs.
- Swap the classifier while keeping the hardware fixed, then measure how much of the score gap comes from software instead of the recorder.
- Test daytime versus nighttime recordings to see how background noise and species mix change performance.
Learn More
- Xeno-canto: A free bird sound archive with labels for building and testing species-ID benchmarks, search the Xeno-canto site.
- Macaulay Library: A free wildlife audio and photo collection from the Cornell Lab, find it through the Cornell Lab of Ornithology site.
- BirdNET: A free bird sound classifier and project page that helps you compare open-source tools, search the BirdNET site and PubMed for papers that use it.
- PubMed: Search review articles on bioacoustics, soundscape ecology, and automatic species recognition.
- MIT OpenCourseWare: Search audio signal processing and machine learning courses for the basics behind spectrograms and classifiers.
