mirror of
https://github.com/deepseek-ai/DeepSeek-Coder.git
synced 2026-11-05 00:57:19 +00:00
[GH-ISSUE #3] Discussion about possible contamination? #2
Labels
No labels
documentation
ENV
pull-request
research question
WIP
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-Coder#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zkx06111 on GitHub (Nov 2, 2023).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-Coder/issues/3
Hi, I appreciate your great contribution to the open-source community!
I wonder if there's any measure you took to prevent contamination in your training corpus or any discussion about it in your technical report.
Thanks
@guoday commented on GitHub (Nov 4, 2023):
What's meaning of contamination? Do you mean low-quality code?
@jeff31415 commented on GitHub (Nov 4, 2023):
I think he/she means the potential leak of eval sets(eg Human Eval) into pretaining corpus, and the effectiveness of benchmark, sience achievening 79% pass@1 on HumanEval is not common before.🤔
@guoday commented on GitHub (Nov 4, 2023):
I see. We use the same method as https://github.com/bigcode-project/bigcode-dataset/tree/main/decontamination.
As we said here, we apply the same filtering rules as StarcoderData to filter data, including decontamination.
@zkx06111 commented on GitHub (Nov 5, 2023):
Thanks for the clarification!