atefehsz commited on
Commit
d3d0fcc
·
verified ·
1 Parent(s): 3000631

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +1 -1
README.md CHANGED
@@ -36,7 +36,7 @@ The use of this model is governed by the [NVIDIA AI Foundation Models Community
36
  - **Pooling mode:** mean tokens
37
 
38
  ## Evaluation Results:
39
- We evaluated NV-EmbedCode model using the [CoIR benchmark](https://arxiv.org/html/2407.02883v1) and a curated set based on [SWE-bench](https://arxiv.org/abs/2310.06770). CoIR consists of 10 code datasets across four retrieval tasks: (1) Text-to-Code Retrieval, (2) Code-to-Code Retrieval, (3) Code-to-Text Retrieval, and (4) Hybrid Code Retrieval. The default evaluation metric for CoIR is average NDCG@10 across all datasets. SWE-bench originally consists of real-world software engineering problems from GitHub issues and their corresponding pull requests. We adapted it into a retrieval task, where the goal is to identify the files that need to be edited to resolve an issue. These files are identified using the pull request that solved the issue. For SWE-bench Lite, we use Recall@1 to measure whether the top retrieved file is the correct one for resolving the issue, as each instance typically involves editing just one file. For more detailed evaluation results on SWE-bench, please refer to [our paper](https://openreview.net/forum?id=k6p8UKRdH7).
40
  <br>
41
 
42
  | Retrieval Method | CoIR Main Score (NDCG@10) | SWE-bench Lite (Recall@1) |
 
36
  - **Pooling mode:** mean tokens
37
 
38
  ## Evaluation Results:
39
+ We evaluated NV-EmbedCode model using the [CoIR benchmark](https://aclanthology.org/2025.acl-long.1072/) and a curated set based on [SWE-bench](https://openreview.net/forum?id=VTF8yNQM66). CoIR consists of 10 code datasets across four retrieval tasks: (1) Text-to-Code Retrieval, (2) Code-to-Code Retrieval, (3) Code-to-Text Retrieval, and (4) Hybrid Code Retrieval. The default evaluation metric for CoIR is average NDCG@10 across all datasets. SWE-bench originally consists of real-world software engineering problems from GitHub issues and their corresponding pull requests. We adapted it into a retrieval task, where the goal is to identify the files that need to be edited to resolve an issue. These files are identified using the pull request that solved the issue. For SWE-bench Lite, we use Recall@1 to measure whether the top retrieved file is the correct one for resolving the issue, as each instance typically involves editing just one file. For more detailed evaluation results on SWE-bench, please refer to [our paper](https://openreview.net/forum?id=k6p8UKRdH7).
40
  <br>
41
 
42
  | Retrieval Method | CoIR Main Score (NDCG@10) | SWE-bench Lite (Recall@1) |