Andreas, these are interesting ideas; I wonder whether some kind of
"HOWTO use RAG to improve your ns-3 LLM queries" might be useful to
maintain, starting with your document?
Another recently published direction to consider is to apply a filter on
top of LLM output to fix its errors:
https://arxiv.org/pdf/2409.00676
I was also in a recent discussion in which the topic of trying to use
LLMs to generate first drafts of our missing documentation came up
(e.g., missing chapters in the Sphinx documentation). Of course,
maintainers would have to review/correct what the LLMs generate.
- Tom
On 11/26/24 09:29, Andreas Boltres wrote:
> *[2/2] /[will post this as an answer once the first half of the post is
> approved] /*
>
> I created a custom GPT with access to a single .txt context file [2] and
> custom answering instructions ("ns3_gpt_instructions.txt"). I queried it
> for two different made-up tasks related to packets and shared links to
> the chat:
>
> 1. /Measuring end-to-end delays of individual packets/ (custom GPT [3a]
> vs. default GPT 4o [3b])
> 2. /Retrieve the size of a packet's payload when not knowing which
> headers/trailers exist /(custom GPT [4a] vs. default GPT 4o [4b])