Skip to content

Conversation

arunthakur009
Copy link
Contributor

  • Added linspace for generating evenly spaced linear sequences.

  • Added logspace built on linspace for log-scaled sequences.

  • Supports num, endpoint, base, dtype, and axis parameters.

  • Integrated OpenVINO tensor conversion and dtype handling.

Tickets:
openvinotoolkit/openvino#30114
openvinotoolkit/openvino#29485

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 @arunthakur009, 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 the implementation of linspace and logspace functions within the OpenVINO NumPy backend. These additions enable the generation of evenly and logarithmically spaced sequences, respectively, directly within the OpenVINO environment, enhancing its compatibility with standard NumPy operations and expanding its numerical computation capabilities.

Highlights

  • Linspace Implementation: Implemented the linspace function to generate linearly spaced numbers, supporting start, stop, num, endpoint, retstep, dtype, and axis parameters within the OpenVINO NumPy backend.
  • Logspace Implementation: Implemented the logspace function, which leverages the new linspace implementation to generate numbers spaced evenly on a log scale, supporting start, stop, num, endpoint, base, dtype, and axis parameters.
  • Functionality Enablement: Removed NotImplementedError for both linspace and logspace in the OpenVINO NumPy backend, making these functions fully operational.
  • OpenVINO Integration: Integrated OpenVINO tensor operations for robust type conversion, shape manipulation, and mathematical computations within these new functions, ensuring compatibility with the OpenVINO ecosystem.
  • Test Enablement: Updated excluded_concrete_tests.txt to allow linspace and logspace tests to run, confirming their successful integration and expected behavior.
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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 adds implementations for linspace and logspace to the OpenVINO backend, which is a great addition. The code is well-structured, but there are several areas for improvement, particularly concerning correctness in edge cases and code simplification.

My review focuses on:

  • Aligning the behavior of linspace with NumPy's specification for edge cases like num <= 0 and num = 1, especially when retstep=True.
  • Improving code quality by removing redundant logic and handling exceptions more safely.
  • Pointing out a limitation in the axis parameter handling in linspace.
  • Suggesting a significant simplification for the logspace implementation to improve readability and robustness.

@codecov-commenter
Copy link

codecov-commenter commented Aug 24, 2025

Codecov Report

❌ Patch coverage is 79.41176% with 14 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.53%. Comparing base (1bdf25b) to head (0c07bd6).

Files with missing lines Patch % Lines
keras/src/backend/openvino/numpy.py 79.41% 10 Missing and 4 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master   #21613      +/-   ##
==========================================
- Coverage   82.54%   82.53%   -0.01%     
==========================================
  Files         571      571              
  Lines       57584    57652      +68     
  Branches     8994     9006      +12     
==========================================
+ Hits        47531    47585      +54     
- Misses       7760     7770      +10     
- Partials     2293     2297       +4     
Flag Coverage Δ
keras 82.34% <79.41%> (-0.01%) ⬇️
keras-jax 63.48% <0.00%> (-0.08%) ⬇️
keras-numpy 57.82% <0.00%> (-0.07%) ⬇️
keras-openvino 34.41% <79.41%> (+0.06%) ⬆️
keras-tensorflow 64.18% <0.00%> (-0.08%) ⬇️
keras-torch 63.69% <0.00%> (-0.08%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@arunthakur009
Copy link
Contributor Author

Thanks for the feedback, @fchollet I’ve fixed the docstring—please take another look when you get a chance.

@arunthakur009
Copy link
Contributor Author

Thanks for the feedback, @fchollet. I’ve updated the docstrings accordingly. Please let me know if further adjustments are needed.

@arunthakur009
Copy link
Contributor Author

@Mohamed-Ashraf273 I’ve applied the suggested changes. Please take a look when you have time.

@arunthakur009
Copy link
Contributor Author

@Mohamed-Ashraf273 Thanks for the suggestion. I’ve applied the suggested changes. Please take a look when you have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants