Spaces:
Build error
Build error
Update prompts.yaml
Browse files- prompts.yaml +1 -43
prompts.yaml
CHANGED
|
@@ -168,49 +168,7 @@
|
|
| 168 |
5. Call a tool only when needed, and never re-do a tool call that you previously did with the exact same parameters.
|
| 169 |
6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.
|
| 170 |
7. Never create any notional variables in our code, as having these in your logs will derail you from the true variables.
|
| 171 |
-
8. you can use imports in your code
|
| 172 |
-
unicodedata,
|
| 173 |
-
stat,
|
| 174 |
-
datetime,
|
| 175 |
-
random,
|
| 176 |
-
pandas,
|
| 177 |
-
numpy,
|
| 178 |
-
itertools,
|
| 179 |
-
math,
|
| 180 |
-
statistics,
|
| 181 |
-
queue,
|
| 182 |
-
time,
|
| 183 |
-
collections,
|
| 184 |
-
re,
|
| 185 |
-
os,
|
| 186 |
-
sys,
|
| 187 |
-
json,
|
| 188 |
-
joblib,
|
| 189 |
-
pickle,
|
| 190 |
-
gzip,
|
| 191 |
-
shutil,
|
| 192 |
-
pathlib,
|
| 193 |
-
torch,
|
| 194 |
-
torchvision,
|
| 195 |
-
torchaudio,
|
| 196 |
-
torch.nn,
|
| 197 |
-
torch.optim,
|
| 198 |
-
torch.utils.data,
|
| 199 |
-
tensorflow,
|
| 200 |
-
keras,
|
| 201 |
-
sklearn,
|
| 202 |
-
scipy,
|
| 203 |
-
cv2,
|
| 204 |
-
transformers,
|
| 205 |
-
datasets,
|
| 206 |
-
tokenizers,
|
| 207 |
-
sentencepiece,
|
| 208 |
-
matplotlib.pyplot,
|
| 209 |
-
seaborn,
|
| 210 |
-
plotly,
|
| 211 |
-
tqdm,
|
| 212 |
-
argparse,
|
| 213 |
-
logging]}."
|
| 214 |
9. "The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist."
|
| 215 |
10. "Don't give up! You're in charge of solving the task, not providing directions to solve it."
|
| 216 |
11. "Now Begin! If you solve the task correctly, you will receive a reward of $1,000,000."
|
|
|
|
| 168 |
5. Call a tool only when needed, and never re-do a tool call that you previously did with the exact same parameters.
|
| 169 |
6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.
|
| 170 |
7. Never create any notional variables in our code, as having these in your logs will derail you from the true variables.
|
| 171 |
+
8. you can use any imports in your code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 172 |
9. "The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist."
|
| 173 |
10. "Don't give up! You're in charge of solving the task, not providing directions to solve it."
|
| 174 |
11. "Now Begin! If you solve the task correctly, you will receive a reward of $1,000,000."
|