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

Two components of LLMcoder #16

Closed
psaegert opened this issue Nov 15, 2023 · 1 comment
Closed

Two components of LLMcoder #16

psaegert opened this issue Nov 15, 2023 · 1 comment

Comments

@psaegert
Copy link
Collaborator

I've come to think that it may be best if we divide the LLMcoder copletion pipeline into two parts using two models:

  1. The fine-tuned (Fine-Tuning #6) autocomplete model provides the first code suggestion as a consistently formatted and reliable baseline
  2. The "feedback" model (maybe the regular gpt-3.5-turbo) continues the conversation with
    • analysis results or a "reflect"-prompt (detection)
    • a "fix this issue"-prompt (fixing)

We may need to evaluate how consistent the model is in feedback-mode, and if it suffers from the same problems regarding the format of the output and modifications of previous code (maybe we need to fine-tune another variant for the feedback-loop?)

@psaegert
Copy link
Collaborator Author

Applied in #23, #28

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

No branches or pull requests

1 participant