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
Category Encoding Layer #6855
Category Encoding Layer #6855
Conversation
* Category Encoding Preprocessing Layer Co-authored-by: David Kim (@koyykdy) <dok098@ucsd.edu> Brian Zheng (@Brianzheng123) <brianzheng345@gmail.com>
@mattsoulanille I was hoping to get a review of this whenever you are available to. Thank you! |
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.
Thanks for the PR! I have a few changes for you to take a look at. Feel free to @ me immediately in future PRs, or when you're ready for me to take another look, and I'll respond sooner.
@mattsoulanille Thank you for the review! I'll ping you once these changes have been implemented |
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
* revision for catencoding pr * fixed tests and reviewer reccomendations * fixed changed files for clean pr
* revision for catencoding pr * fixed tests and reviewer reccomendations * fixed changed files for clean pr * fixed indentation and linting error * fixed return statement in preprocessing function
Hi @mattsoulanille I made the requested changes and checked that the linter was passing via |
Looks like it's failing one of the bounds tests:
This is strange; the two error messages look identical to me (unless I've just completely missed something). Same for output mode tests:
The failures are reproducible locally with Edit: add url |
Oh, I see the issue. JS does not let you wrap strings by just adding a newline in them. Well, it does, but it includes the newline and all the indentation spaces. You'll need to split those strings into multiple different strings that you add together. I'll add an example. |
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.
Quick review showing how to fix the multiline string errors. I'll do a full review in a bit.
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
* fixed indentation and linting error * fixed return statement in preprocessing function * fixed multiline error message in preprocessing_utils.ts
* passing all unit tests
* revision for catencoding pr * fixed tests and reviewer reccomendations * fixed changed files for clean pr * fixed indentation and linting error * fixed return statement in preprocessing function * commit change before upstream * fixed multiline error message in preprocessing_utils.ts * passing all unit tests * fixed int string
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.
LGTM with a few nits. Thanks!
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
Co-authored-by: Matthew Soulanille <matthew@soulanille.net>
* added reviewer requests
@mattsoulanille I just updated the branch and it caused the build to fail. Please let me know if there is something I can fix. Thanks for all of the help! |
@AdamLang96 We just changed some GCP Cloudbuild permissions and they accidentally broke CI for a few minutes. Should be fixed now, so I'll re-run the tests. |
David Kim (@koyykdy) dok098@ucsd.edu
Brian Zheng (@Brianzheng123) brianzheng345@gmail.com
To see the logs from the Cloud Build CI, please join either our discussion or announcement mailing list.
This change is