Skip to content
New issue

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

Create a "predict.py" that generally works for TCN #294

Open
cameron-a-johnson opened this issue Sep 21, 2023 · 0 comments
Open

Create a "predict.py" that generally works for TCN #294

cameron-a-johnson opened this issue Sep 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@cameron-a-johnson
Copy link
Collaborator

Lesson learned from the 9/22/23 demo:

The latest experiments were testable via PyTorch Lightning's validation pipeline during training, so we've been able to collect performance metrics via training runs.

Then there was friction when pulling out a "predict" function to plug into the live system.

This wasn't done via Lightning for the 9/22/23 demo, because Lightning's predict call was not working properly. So a predict call was instead hand-crafted, and we hit bumps including not normalizing pixel-wise distances property for the TCN's feature vector, using [tlbr] instead of [xywh] to capture bounding box position & size, etc...

But calling any of our trained TCN models via lightning should be possible with one call.
https://stackoverflow.com/questions/65807601/output-prediction-of-pytorch-lightning-model

Let's get that "predict.py" call ready for the next time we need it, ideally in a way that's generalizable to any of our feature vector versions.

@cameron-a-johnson cameron-a-johnson added the enhancement New feature or request label Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant