SCRUM-43: Integrated MesoNet into Ensemble#24
Open
frank-bi-canada wants to merge 9 commits intomainfrom
Open
Conversation
added 9 commits
February 23, 2026 15:47
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.
Jira Ticket
SCRUM-43: Integrated MesoNet into Ensemble
Summary
MesoNet can now take faces from video_handler.py and output a result. Currently the result is unused.
Due to the large differences in the virtual environments of the ensemble and MesoNet, communication between the two is facilitated through HTTP requests. The Python 3.6 mesonet environment will be run on a server (current default of port 8000) and provide a client that imitates some functions of a PyTorch model.
Docs Updated
docs/models/<model>/01-model-notes.mddocs/models/<model>/02-source-and-setup.mddocs/datasets/candidates.mddocs/datasets/selected.mdWhat You Verified
Running the main ensemble (excluding using other models) will correctly start the mesonet server and produce a valid output. Stopping the server may fail on some errors, but handling this error may depend on how the facial_analyzer.py processing function is implemented and used in the future. The current solution is to kill the server process (see
docs/models/<model>/02-source-and-setup.mdIssues encountered + fixes).Commands Run (if any)
Exact command usage and outputs provided in source-and-setup.md for MesoNet.
Screenshots Added?
assets/and referenced in markdownChecklist
assets/and referenced in markdown (if any).gitignorerules)