Skip to content

Add code snippet for embeddings normalization #13507

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Tengxin-Li
Copy link

Description

Add code snippet for embeddings normalization, so that the magnitude of the array is always 1.

Checklist

@Tengxin-Li Tengxin-Li requested review from a team as code owners July 16, 2025 18:54
@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Jul 16, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @Tengxin-Li, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new utility module to the generative_ai/embeddings directory. Its primary purpose is to provide a robust method for normalizing embedding vectors, ensuring their consistent magnitude for downstream machine learning tasks that rely on normalized representations.

Highlights

  • New Utility Function: I've added a new Python function, normalize_embedding, designed to normalize NumPy array embeddings to have an L2 norm (magnitude) of 1.
  • Numerical Stability: The normalize_embedding function includes a check to handle cases where the input embedding's magnitude is zero, returning the original array to prevent division by zero errors.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new utility function to normalize embeddings. The implementation is clear, but I have a couple of suggestions to improve its robustness and maintainability.

My main concerns are:

  1. The use of direct floating-point comparison, which can be unreliable.
  2. The absence of unit tests for the new functionality, which is crucial for ensuring correctness.

Please see my detailed comments in the code. Addressing these points will make the new code more robust and easier to maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
samples Issues that are directly related to samples.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant