Skip to content

Commit 91433d0

Browse files
committed
fix: update README
1 parent 9ec75e0 commit 91433d0

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ bigcodebench.generate \
103103
The generated code samples will be stored in a file named `[model_name]--bigcodebench-[nl2c|c2c]--[backend]-[temp]-[n_samples].jsonl`. Alternatively, you can use the following command to utilize our pre-built docker images for generating code samples:
104104
>
105105
```shell
106-
docker run --gpus '"device=$CUDA_VISIBLE_DEVICES"' -v $(pwd):/bigcodebench -t codeeval/code-eval-generate-cu11:25052024 --model [model_name] \
106+
docker run --gpus '"device=$CUDA_VISIBLE_DEVICES"' -v $(pwd):/bigcodebench -t terryzho/bigcodebench-generate-cu11:25052024 --model [model_name] \
107107
--subset [c2c|nl2c] \
108108
--greedy \
109109
--bs [bs] \
@@ -119,7 +119,7 @@ We make available `cuda 11.8.0` and `cuda 12.1.1` pre-built docker images with t
119119
If you wish to use gated or private HuggingFace models and datasets, you need to build the container yourself with `--build-arg` flags as follows:
120120
>
121121
```shell
122-
docker build --build-arg HF_TOKEN=<YOUR_HF_TOKEN> -t codeeval/code-eval-generate-cu11:latest - < Docker/Generate_Cuda11.Dockerfile
122+
docker build --build-arg HF_TOKEN=<YOUR_HF_TOKEN> -t terryzho/bigcodebench-generate-cu11:latest - < Docker/Generate_Cuda11.Dockerfile
123123
```
124124
>
125125
Following which, you can run the built container as shown in above.
@@ -160,7 +160,7 @@ bigcodebench.sanitize --samples /path/to/vicuna-[??]b_temp_[??]
160160
# Sanitized code will be produced to `/path/to/vicuna-[??]b_temp_[??]-sanitized`
161161
```
162162

163-
<details><summary>🔎 Checking the compilability of post-processed code<i>:: click to expand ::</i></summary>
163+
<details><summary>🔎 Checking the compatibility of post-processed code<i>:: click to expand ::</i></summary>
164164
<div>
165165

166166
To double-check the post-processing results, you can use `bigcodebench.syncheck` to check the code validity before and after sanitization, which will print erroneous code snippets and why they are wrong:
@@ -183,9 +183,9 @@ You are strongly recommended to use a sandbox such as [docker](https://docs.dock
183183

184184
```shell
185185
# mount the current directory to the container
186-
docker run -v $(pwd):/bigcodebench codeeval/code-eval-evaluate:latest --dataset bigcodebench --samples samples.jsonl
186+
docker run -v $(pwd):/bigcodebench terryzho/bigcodebench-evaluate:latest --subset [c2c|nl2c] --samples samples.jsonl
187187
# ...Or locally ⚠️
188-
bigcodebench.evaluate --dataset bigcodebench --samples samples.jsonl
188+
bigcodebench.evaluate --subset [c2c|nl2c] --samples samples.jsonl
189189
```
190190

191191
...Or if you want to try it locally regardless of the risks ⚠️:
@@ -199,7 +199,7 @@ pip install -r https://raw.githubusercontent.com/bigcode-project/bigcodebench-an
199199
Then, run the evaluation:
200200

201201
```shell
202-
bigcodebench.evaluate --dataset [bigcodebench] --samples samples.jsonl
202+
bigcodebench.evaluate --subset [c2c|nl2c] --samples samples.jsonl
203203
```
204204

205205
> [!Tip]

0 commit comments

Comments
 (0)