-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
refactor: Simplify model export #73
Conversation
Replaces OutputMapperLayer with a custom serving function. This means we don't need to save two models (training/serving) anymore, as the (ex training) model will do the "output mapping" through the custom serving function. With this approach, we could even have multiple serving functions with different output mapping strategies.
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
I'd love to get feedback on the proposed refactoring. It's not a fluid as I'd like, but my feeling is it's going in the right direction (?). I put a few FIXME in the comments where things are still a bit rough. Comments welcome! |
Ready for rewiew. Hopefully it's at least as readable as pre-refactoring 😅 There are inconsistencies in the run timestamps because I had to fix a memory crash in the "Test" section and didn't want to re-run the full 2h of model training. It's only cosmetic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, I just suggested some minor changes.
Replaces OutputMapperLayer with a custom serving function.
This means we don't need to save two models (training/serving)
anymore, as the (ex training) model will do the "output mapping"
through the custom serving function.
With this approach, we could even have multiple serving functions with
different output mapping strategies.