You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Figure 3, the paper compare naive RAG, advanced RAG and modular RAG. In advanced RAG, the paper list query routing, rewriting and expansion in pre-retrieval phase, and rerank, summary and fusion in post-retrieval phase. But all of them are not mentioned in the Advanced RAG (3.2) section. Most of them are mentioned in Modular RAG instead. I'm a bit confused. Can anyone elaborate more on this?
Serving as a survey on the field that requires alignments everywhere, the paper should align well to itself, shouldn't it?
The text was updated successfully, but these errors were encountered:
We believe that Modular RAG represents the inheritance and development of the Advanced RAG paradigm.
Difference: Compared to its predecessor, Modular RAG enriches the process beyond the simple retrieve-then-generate approach. It integrates many new functional modules, such as using generated content to replace retrieval.
Inheritance: Common modules from Advanced RAG, such as Rewrite and Rerank, still play an important role in Modular RAG.
In the survey composition, to emphasize Modular RAG, we reduced the introduction to some aspects of Advanced RAG. We apologize for any misunderstanding this may have caused.
We hope the new version of the manuscript and my response will be helpful to you.
In Figure 3, the paper compare naive RAG, advanced RAG and modular RAG. In advanced RAG, the paper list query routing, rewriting and expansion in pre-retrieval phase, and rerank, summary and fusion in post-retrieval phase. But all of them are not mentioned in the Advanced RAG (3.2) section. Most of them are mentioned in Modular RAG instead. I'm a bit confused. Can anyone elaborate more on this?
Serving as a survey on the field that requires alignments everywhere, the paper should align well to itself, shouldn't it?
The text was updated successfully, but these errors were encountered: