Re:Exploring GPTs: ChatGPT in a trench coat?
by IanCal on Wednesday November 15, 2023 @02:29PM
(#38281243)
I've had good success putting code examples in a single txt file for our custom framework, and it seems to use that neatly for generating code. I'm surprised you've not had much success with them, I gave an assistant my wife's PhD thesis and while the API was working initially it seemed alright.
Re:Exploring GPTs: ChatGPT in a trench coat?
by wddkcs on Wednesday November 15, 2023 @03:34PM
(#38282052)
Does that error message really confirm qdrant for Chat? It's just failing to index a file called 'qdrant', and I don't see any further proof offered in that thread.
Re:Exploring GPTs: ChatGPT in a trench coat?
by simonw on Wednesday November 15, 2023 @03:48PM
(#38282237)
That's good enough evidence for me.
They're clearly running a vector store (you can get further hints at that by spying on the JSON using browser DevTools).
Qdrant is a very good vector store - it's powering all of the new Twitter features as of a few weeks ago.
Seems much more likely to me that they're using Qdrant than this is a weird error message coincidence.
Re:Exploring GPTs: ChatGPT in a trench coat?
by jjwiseman on Wednesday November 15, 2023 @04:04PM
(#38282462)
Interestingly, when I used an .md extension, GPT would write python code to try to pull parts out to answer queries (which worked miserably), but when I used .txt (for the same files), it seemed to put it in the vector store.
We know it's Qdrant because an error message leaked that detail: https://twitter.com/altryne/status/1721989500291989585
It only applies that mechanism to some file types though - PDFs and .md files for example.
Other file formats that you upload are stored and made available to Code Interpreter but are not embedded for vector search.