Tabtransformer #33
Merged
Tabtransformer #33
Conversation
This file contains 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
…tween a number of implementation (that will of course be credited in the code)
…e remaining tests
…0 for unseen categories (as padding) for both wide and deeptabular component
…k and fix bug in the History callback. Added multiple tests and increased code coverage to 94 per cent
…ch I really like. Changed the code accordingly. Changed the name of DeepDense and DeepDenseResnet to TabMlp and TabResnet. Change the tests acccordingly
… ones if required. Now I need to think if I want it registered as a child or not. Also, need to test all new implementation
… a Trainer class. All seems easier now. Need to adjust all documentation. Also added a few losses and an R2 metric, as well as the possibiliy of customising virually every single component of the model
… new code structure. Remove partial imports from...everywhere. Updated examples
…ixed some examples of usage. Added FullEmbeddingDropout to TabTransformer. Encapsulate alias in Classes in loss_and_obj_alias module and change some minor style text
…o latest version of numpy (need to look into this. Ready to move on with notebooks
…of callback tests, since it seems to cause some problems at testing time (I think, see what travis has to say)
…hat it really is, FineTune. Alias the corresponding parameters so that the user can use both, finetune and alias params. Modified a few defaults
…tirely diff when built in the locally than with the app, I had to revert back to default themes. This was painful
…Read The Docs app, who knows why
… beta because I prefer to wait for V1 until I have tried it with more datasets
…ine types. Ready to publish
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.
This represents an almost-complete refactor of the previous version and I consider the code in this version well tested and production-ready. The only reason why this release is not v1 is because I want to use it with a few more datasets, but at the same time I want the version to be public to see if others use it. This version is not backwards compatible (at all).
These are some of the structural changes:
TabTransformeras a potentialdeeptabularcomponent