Validate EfficientNetV2 MQTT inference in Docker#899
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I updated the Engine inference flow to use the local EfficientNetV2 TFLite prediction path instead of the old TensorFlow Serving
outputsformat. The Engine now produces predicted species labels, confidence values, and top predictions from MQTT audio messages.Files Changed
light_echo_engine_efficientnetv2_tflite.pyUpdated MQTT audio inference to use EfficientNetV2 TFLite locally.
system_manager.pyFixed simulator start mode handling.
control_sim.pyUpdated simulator testing flow for
Animal_Mode.comms_manager.pyAdded debug checks to confirm valid WAV audio was being sent.
Engine requirements file
Updated Engine dependencies needed for Docker/TFLite inference.
Simulator requirements file
Updated Simulator dependencies needed for MQTT/audio testing.
README_EfficientNetV2_Engine_Integration.mdUpdated final Docker/MQTT validation status.
Note
The remaining
Internal Server Errorhappens after prediction when sending results to the API/database, so it appears to be an API/backend issue.