RAG is an abbreviation of Retrieval Augmented Generation. Let’s breakdown this term to get a clear overview of what RAG is:
R -> Retrieval
A -> Augmented
G -> Generation
So basically, the LLM that we use today is not up to the date. If I ask a question to a LLM let’s say ChatGPT, it may be hallucinated and give us the incorrect answer. To overcome this situation, we train our LLM with some more data(data which is only accessible to limited people, not globally). Then we ask some questions to the LLM trained on that data. Surely, it will give us the relevant information. Here are the some situation that may occur if we don’t use RAG:
Increasing possibility of hallucination
LLM is outdated
Reduced Accuracy and Factual information
You can have a look at the diagram mentioned below:
RAG is a hybrid system which combines the strength of a retrieval based system with LLMs to generate more accurate, relevant and informed decisions. This method leverages external knowledge sources during the generation process, enhancing the model’s ability to provide up-to-date and contextually appropriate information. In the above diagram:
In the first step, the user asks the query to the LLM.
The query is then sent to the
The
The retrieved documents, along with the original query, are sent to the language model (LLM).
The generator processes both the query and the relevant documents to generate a response, which is then sent back to the user.
Now I know you are fully interested in learning RAG from basic to advanced. Now let me tell you the perfect roadmap to learn RAG in just 5 days. Yes, you heard it right, in just 5 days you can learn the RAG system. Let’s dive straight into the roadmap:
Day 1: Build a Foundation for RAG
The core objective of day 1 is understanding the RAG at a high level and exploring what are the key components of RAG. Below are the breakdown of the topics for day 1
Overview of RAG:
Recognize RAG’s functions, significance, and place in contemporary NLP.
The main idea is that retrieval-augmented generation improves generative models by incorporating outside information.
Key Components:
Learn about retrieval and generation separately.
Look into the architectures for both retrieval (e.g., dense passage retrieval (DPR), BM25) and generation (e.g., GPT, BART, T5).
Day 2: Building your own Retrieval System
The core objective of day 2 is to Successfully implement a retrieval system (even a basic one).Below are the breakdown of the topics for day 2
Deep Dive into Retrieval Models:
Learn about Dense Retrieval vs. Sparse Retrieval:
Dense: DPR, ColBERT.
Sparse: BM25, TF-IDF.
Discover the advantages and disadvantages of each method.
Implementation of Retrieval:
Use libraries such as elasticsearch for sparse retrieval or faiss for dense retrieval to carry out basic retrieval tasks.
Work through Hugging Face’s DPR tutorial to understand how to retrieve relevant documents from a knowledge base.
Knowledge Databases:
Understand how knowledge bases are structured.
Learn how to prepare data for retrieval tasks, such as pre-processing a corpus and indexing documents.
Day 3: Fine-tune a generative model and observe the results
The goal of day 3 is to Fine-tune a generative model and observe the results. Understand the role of retrieval in augmenting generation. Below are the breakdown of the topics for day 3
Deep Dive into Generative Models:
Examine trained models such as T5, GPT-2, and BART.
Learn the fine-tuning process for generation tasks such as question-answering or summarization.
Hands-on with Generative Models:
Apply the transformers provided by Hugging Face to refine a model on a short dataset.
Test generating answers to questions using the generative model.
Exploring the Interaction Between Retrieval and Generation:
Examine the generative model’s input methods for retrieved data.
Recognize how retrieval enhances the precision and caliber of responses that are generated.
Day 4: Implement a working RAG system
Now, we are getting closer to the goal. The main objective of this day is to Implement a working RAG system on a simple dataset and Gain familiarity with tweaking parameters.Below are the breakdown of the topics for day 4
Combining Retrieval and Generation:
Combine the components for generation and retrieval into a single system.
Implement the interaction between retrieval outputs and the generative model.
Using Llamaindex’s RAG Pipeline:
Go through the official documentation or a tutorial to learn how the RAG pipeline functions.
Utilizing LlamaIndex’s RAG model, set up and execute an example.
Hands-on Experimentation:
Start experimenting with different parameters like the number of documents retrieved, beam search strategies for generation, and temperature scaling.
Try running the model on simple knowledge-intensive tasks
Day 5: Build and Fine-tune a More Robust RAG System
The goal of this last day to create a more robust RAG model by Finetuning it and get knowledge about the different types of RAG models that you can explore. Below are the breakdown of the topics for day 5
Advanced Fine-Tuning: Examine how to optimize the generation and retrieval components for tasks that are specific to a given domain.
Scaling Up: Use bigger datasets and more intricate knowledge bases to increase the size of your RAG system.
Performance Optimization: Learn how to maximize memory consumption and retrieval speed (for example, by utilizing faiss with GPU).
Evaluation: Acquire the skillset to assess RAG models in knowledge-intensive jobs. utilizing various metrics BLEU, ROUGE, and more measures for addressing questions.
End Note
By following this roadmap, you can learn the RAG system within 5 days depending upon your learning capabilities. I hope you like this roadmap. I usually share Generative AI stuff in the form of a carousel or you can say a bit sized informative post. You can check more carousels on my Linkedin Profile.
’m a Generative AI enthusiast, exploring the limitless possibilities of Generative AI, where creativity meets technology. With a passion for the evolving landscape of artificial intelligence, I dive deep into the innovations shaping our future, from text generation to creative visualizations. Continuously fascinated by the intersection of machine learning and human ingenuity, I’m driven by a curiosity to understand and contribute to this ever-growing field.
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
Powered By
Cookies
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
brahmaid
It is needed for personalizing the website.
csrftoken
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Identityid
Preserves the login/logout state of users across the whole site.
sessionid
Preserves users' states across page requests.
g_state
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
MUID
Used by Microsoft Clarity, to store and track visits across websites.
_clck
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_clsk
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
SRM_I
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
SM
Use to measure the use of the website for internal analytics
CLID
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
SRM_B
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
_gid
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
_ga_#
Used by Google Analytics, to store and count pageviews.
_gat_#
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
collect
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
AEC
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
G_ENABLED_IDPS
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
test_cookie
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
_we_us
this is used to send push notification using webengage.
WebKlipperAuth
used by webenage to track auth of webenagage.
ln_or
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
JSESSIONID
Use to maintain an anonymous user session by the server.
li_rm
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
lms_analytics
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
liap
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
visit
allow for the Linkedin follow feature.
li_at
often used to identify you, including your name, interests, and previous activity.
s_plt
Tracks the time that the previous page took to load
lang
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
s_tp
Tracks percent of page viewed
AMCV_14215E3D5995C57C0A495C55%40AdobeOrg
Indicates the start of a session for Adobe Experience Cloud
s_pltp
Provides page name value (URL) for use by Adobe Analytics
s_tslv
Used to retain and fetch time since last visit in Adobe Analytics
li_theme
Remembers a user's display preference/theme setting
li_theme_set
Remembers which users have updated their display / theme preferences
We do not use cookies of this type.
_gcl_au
Used by Google Adsense, to store and track conversions.
SID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
SAPISID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
__Secure-#
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
APISID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
SSID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
HSID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
DV
These cookies are used for the purpose of targeted advertising.
NID
These cookies are used for the purpose of targeted advertising.
1P_JAR
These cookies are used to gather website statistics, and track conversion rates.
OTZ
Aggregate analysis of website visitors
_fbp
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
fr
Contains a unique browser and user ID, used for targeted advertising.
bscookie
Used by LinkedIn to track the use of embedded services.
lidc
Used by LinkedIn for tracking the use of embedded services.
bcookie
Used by LinkedIn to track the use of embedded services.
aam_uuid
Use these cookies to assign a unique ID when users visit a website.
UserMatchHistory
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
MR
Used to collect information for analytics purposes.
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
We do not use cookies of this type.
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.