Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

关于cot #90

Open
Violettttee opened this issue Dec 26, 2024 · 7 comments
Open

关于cot #90

Violettttee opened this issue Dec 26, 2024 · 7 comments

Comments

@Violettttee
Copy link

看代码里如果设置了cot,会请求llm两次,是我理解错了吗?为什么会考虑请求两次呢

@bys0318
Copy link
Member

bys0318 commented Dec 29, 2024

你好,cot第一次请求会让模型输出chain of thought (let's think step by step),第二次请求会让模型根据题目以及上一步输出的chain of thought输出最终选择。请参考我们的prompt:https://github.com/THUDM/LongBench/blob/main/prompts/0shot_cot.txt
https://github.com/THUDM/LongBench/blob/main/prompts/0shot_cot_ans.txt

@Violettttee
Copy link
Author

Violettttee commented Dec 29, 2024

@bys0318
你好,收到~有一个小小的疑惑,我看第二次输出最终选择的时候,也有一个think step by step的prompt,但是昨天实际测试的时候发现第二次输出最终选择模型似乎不会再cot了,而是直接回复answer,这里和你们测试其他模型时遇到的情况是一样的吗?另外想请教下这种两次cot会比一次cot更好吗?(看了一下那部分相关的论文好像没有直接提到两次cot的方法,可以请教下出处吗。)

@bys0318
Copy link
Member

bys0318 commented Dec 29, 2024

第二次请求Let’s think step by step: COT的"COT"是要用第一次请求得到的CoT输出替换掉的,第二次请求只是要求模型根据上一次请求得到的CoT总结得到答案。我们在论文附录D中讲了CoT的测试方法,这种方法参考自GPQA

@Violettttee
Copy link
Author

@bys0318
明白~但我疑惑的点主要是为什么没有考虑直接一次cot拿结果呢?

@bys0318
Copy link
Member

bys0318 commented Dec 29, 2024

只用一次prompt应该也可以,但是模型在zero-shot下可能不能很好地follow指令。

@Violettttee
Copy link
Author

@bys0318
明白,感谢~

@guanzhchen
Copy link

你好,cot第一次请求会让模型输出chain of thought (let's think step by step),第二次请求会让模型根据题目以及上一步输出的chain of thought输出最终选择。请参考我们的prompt:https://github.com/THUDM/LongBench/blob/main/prompts/0shot_cot.txt https://github.com/THUDM/LongBench/blob/main/prompts/0shot_cot_ans.txt

请问第二步时是不输入完整的context了是么,只是总结答案而已

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants