-
Notifications
You must be signed in to change notification settings - Fork 20
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
Defaults don't seem to persist to chattr
call
#49
Comments
Hi there, I was running into the similar issue. And, the following methods seems to fix this issue specifically for me. Hope it helps. |
Thanks. Didn't work in my case. |
I made some updates and I think this is fixes now, can you confirm? > chattr_defaults()
── chattr ──────────────────────────────────────────────────────────────────────────
── Defaults for: Default ──
── Prompt:
• Use the R language, the tidyverse, and tidymodels
── Model
• Provider: LlamaGPT
• Path/URL: Library/LlamaGPTJ-chat/build/bin/chat
• Model: Library/ggml-gpt4all-j-v1.3-groovy.bin
── Model Arguments:
• threads: 4
• temp: 0.01
• n_predict: 1000
── Context:
Max Data Files: 0
Max Data Frames: 0
✖ Chat History
✖ Document contents
> chattr("test", preview = TRUE)
── chattr ──────────────────────────────────────────────────────────────────────────
── Preview for: Console
• Provider: LlamaGPT
• Path/URL: Library/LlamaGPTJ-chat/build/bin/chat
• Model: Library/ggml-gpt4all-j-v1.3-groovy.bin
• threads: 4
• temp: 0.01
• n_predict: 1000
── Prompt:
test(Use the R language, the tidyverse, and tidymodels) |
Hi Edgar,
Thanks a lot for looking into it.
We may move to GitHub Copilot and some home-made apps.
Thanks,
Edward
________________________________
发件人: Edgar Ruiz ***@***.***>
发送时间: 2024年3月20日 6:07
收件人: mlverse/chattr ***@***.***>
抄送: Edward Jin ***@***.***>; Comment ***@***.***>
主题: Re: [mlverse/chattr] Defaults don't seem to persist to `chattr` call (Issue #49)
I made some updates and I think this is fixes now, can you confirm?
chattr_defaults()
── chattr ──────────────────────────────────────────────────────────────────────────
── Defaults for: Default ──
── Prompt:
• Use the R language, the tidyverse, and tidymodels
── Model
• Provider: LlamaGPT
• Path/URL: Library/LlamaGPTJ-chat/build/bin/chat
• Model: Library/ggml-gpt4all-j-v1.3-groovy.bin
── Model Arguments:
• threads: 4
• temp: 0.01
• n_predict: 1000
── Context:
Max Data Files: 0
Max Data Frames: 0
✖ Chat History
✖ Document contents
chattr("test", preview = TRUE)
── chattr ──────────────────────────────────────────────────────────────────────────
── Preview for: Console
• Provider: LlamaGPT
• Path/URL: Library/LlamaGPTJ-chat/build/bin/chat
• Model: Library/ggml-gpt4all-j-v1.3-groovy.bin
• threads: 4
• temp: 0.01
• n_predict: 1000
── Prompt:
test(Use the R language, the tidyverse, and tidymodels)
—
Reply to this email directly, view it on GitHub<#49 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQJ6FMKQBVGYJWTTAKJR4JDYZCZIPAVCNFSM6AAAAAA6JU6ZW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBYGIZDCNRYGE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
TLDR; defaults persist now! hi all - I was also running into this issue back in November 2023. I had pivoted to gpt4all via Python.. However, I noticed the chattr changelog (CRAN release: 2024-04-27) and figured I'd read up on the project again. Based on my tests, the edits @edgararuiz mentioned are working! Changed defaults successfully, chattr_test() was successful, and chattr() works as intended now. @edgararuiz thank you! |
Hello! Lovely little idea and package here. Been trying to get it running, but running into some snags.
Let me preface that I've been able to successfully run LlamaGPTJ-chat on the machine so I know that piece is working. I've been able to set the defaults and run
chattr_test()
to see that it's using the correct path and model, however when I go to run chattr from the console, it failed. I used the preview flag and found that it still references the old default directories. Attached screenshots to show.Defaults are correct:
Test is correct and runs, but preview flag shows a different path and therefore fails.
The text was updated successfully, but these errors were encountered: