mirror of
https://github.com/deepseek-ai/DeepSeek-R1.git
synced 2026-11-05 00:47:42 +00:00
[GH-ISSUE #66] Unprofessional style can't be fixed #54
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-R1#54
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 @pannous on GitHub (Jan 24, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/66
The model talks in an unprofessional way and refuses to adhere to style guides given in the system prompt.
as one example in ollama:
@Manamama commented on GitHub (Jan 24, 2025):
A feature, not a bug, maybe.
Just run the output via a very basic LLM downstream, telling it to "professionalise", convert to e.g. basic English, standardize as per X guidelines, translate to R, etc., if needed.
@justinlietz93 commented on GitHub (Jan 25, 2025):
Agreed, you can clean up the output downstream. The language is part of its deep reasoning process to emulate deep thought
@davidogundepo commented on GitHub (Jan 27, 2025):
I actually think the casual style helps the model think through problems better - like how sometimes we talk to ourselves when solving something tricky! I mean sure, we could make it sound super formal and professional, but that might actually make its reasoning less natural.
Think of it like having a really smart friend helping you work through a problem. They might say "Okay, so..." because they're thinking out loud. That's not unprofessional - it's just human!
If someone really needs fancy formal language, they can totally run it through another AI to polish it up. But personally, I'd rather keep that genuine thought process intact.
@github-actions[bot] commented on GitHub (Mar 4, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@github-actions[bot] commented on GitHub (Apr 12, 2025):
false