주소(Address)값을 One Hot Encode해서 적용 #4
Conversation
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.
이전까지는 주소(Address) 컬럼을 사용하지 않았는데, 이번에 새로 적용해보았습니다.
One Hot Encoding을 쓰는게 가장 적합하다고 생각하였고, 메모리 효율과 Ovefitting을 방지하기 위해, 너무 갯수가 적은 주소값은 'Other'라는 값으로 합쳤습니다. (스크립트에서는 200개 이하를 'Other'로 치환)
적용 결과 CV Score는 2.506260로 -0.055880 상승하였고, Public LB Score는 2.48252로 (아마도?) 상승하였습니다. 다른 PR과 합쳐서 사용한다면 더 좋은 결과가 나올 것으로 예상합니다!