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

[Feature] Local Ollama-Deployed Deepseek R1 14B Output Optimization for Zotero Translation #1086

Open
1 task done
LeabaeL opened this issue Feb 9, 2025 · 1 comment
Open
1 task done
Assignees
Labels
enhancement New feature or request

Comments

@LeabaeL
Copy link

LeabaeL commented Feb 9, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Environment

  • OS: Windows 11 24H2
  • Zotero Version: 7.0.11 (64-bit)
  • Plugin Version: 2.1.5

Describe the feature request

Is your feature request related to a problem? Please describe.
I'm experiencing an issue where the locally deployed Deepseek R1 14B model via Ollama includes chain-of-thought details in its outputs when performing translations for Zotero. This results in excessively long and verbose translation results, which are not suitable for practical use.

Why do you need this feature?
I need this feature to ensure that the translation outputs remain concise and focused solely on the final translated text. Removing the chain-of-thought content will enhance clarity and usability, making the translations more efficient for integration with Zotero.

Describe the solution you'd like

The solution you'd like
I would like an option or configuration within the plugin that allows the suppression or exclusion of chain-of-thought reasoning in the final output. Ideally, the model should produce only the final translation result without any internal reasoning details, ensuring a cleaner and more concise output.

Alternatives you've considered
I attempted to use prompt engineering by setting the necessary instructions in the configuration to suppress the chain-of-thought content, but this approach did not have any effect. Manual post-processing to remove the extra content is inefficient and error-prone, so a built-in solution within the plugin itself is the most reliable option.

Anything else?

No response

@LeabaeL LeabaeL added the enhancement New feature or request label Feb 9, 2025
@windingwind
Copy link
Owner

Welcome PR.

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

No branches or pull requests

2 participants