Skip to main content

How translation happens in Transformer architecture

 Encoder:

  • Tokenize the input French phrase using the trained tokenizer.

  • Add tokens to the input on the encoder side.

  • Pass the tokens through the embedding layer.

  • Feed tokens into the multi-headed attention layers.

  • Outputs of the multi-headed attention layers are processed by a feed-forward network.

  • The encoder output represents the structure and meaning of the input sequence.

Decoder:

  • Insert the encoder output into the middle of the decoder to influence self-attention mechanisms.

  • Add a start-of-sequence token to the decoder input.

  • The decoder uses contextual understanding from the encoder to predict the next token.

  • The output of the decoder's self-attention layers is processed by the decoder feed-forward network.

  • Pass the output through a final softmax output layer to get the first token.

  • Continue the loop, passing the output token back to the input to predict the next token.

  • Repeat until the model predicts an end-of-sequence token.

  • The final sequence of tokens can be detokenized into words to obtain the output translation.

Comments

Popular posts from this blog

What is the difference between Elastic and Enterprise Redis w.r.t "Hybrid Query" capabilities

  We'll explore scenarios involving nested queries, aggregations, custom scoring, and hybrid queries that combine multiple search criteria. 1. Nested Queries ElasticSearch Example: ElasticSearch supports nested documents, which allows for querying on nested fields with complex conditions. Query: Find products where the product has a review with a rating of 5 and the review text contains "excellent". { "query": { "nested": { "path": "reviews", "query": { "bool": { "must": [ { "match": { "reviews.rating": 5 } }, { "match": { "reviews.text": "excellent" } } ] } } } } } Redis Limitation: Redis does not support nested documents natively. While you can store nested structures in JSON documents using the RedisJSON module, querying these nested structures with complex condi...

Training LLM model requires more GPU RAM than storing same LLM

Storing an LLM model and training the same model both require memory, but the memory requirements for training are typically higher than just storing the model. Let's dive into the details: Memory Requirement for Storing the Model: When you store an LLM model, you need to save the weights of the model parameters. Each parameter is typically represented by a 32-bit float (4 bytes). The memory requirement for storing the model weights is calculated by multiplying the number of parameters by 4 bytes. For example, if you have a model with 1 billion parameters, the memory requirement for storing the model weights alone would be 4 GB (4 bytes * 1 billion parameters). Memory Requirement for Training: During the training process, additional components use GPU memory in addition to the model weights. These components include optimizer states, gradients, activations, and temporary variables needed by the training process. These components can require additional memory beyond just storing th...

How are vector databases used?

  Vector Databases Usage: Typically used for vector search use cases such as visual, semantic, and multimodal search. More recently, they are paired with generative AI text models for conversational search experiences. Development Process: Begins with building an embedding model designed to encode a corpus (e.g., product images) into vectors. The data import process is referred to as data hydration. Application Development: Application developers utilize the database to search for similar products. This involves encoding a product image and using the vector to query for similar images. k-Nearest Neighbor (k-NN) Indexes: Within the model, k-nearest neighbor (k-NN) indexes facilitate efficient retrieval of vectors. A distance function like cosine is applied to rank results by similarity.