Adds guide for layer filters in the Quantization API

[JyotinderSingh]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @JyotinderSingh, I'm Gemini Code Assist¹! 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 significantly enhances the Keras Quantization API documentation by introducing a comprehensive guide on selective layer quantization. This new section empowers users to apply quantization strategically to specific parts of their models, offering greater control over the trade-off between model performance and size. The guide includes practical examples using both regular expressions and custom functions to define quantization filters, making the API more accessible and flexible for advanced use cases.

Highlights

• Selective Quantization Guide: A new section has been added to the Quantization API guide, demonstrating how to selectively quantize layers using the filters argument.
• Filter Options: The guide illustrates the use of both regex strings and custom callable functions for defining quantization filters, providing flexible control over which layers are quantized.
• Code Example Refinement: A get_model helper function was introduced to streamline model creation examples across the guide, improving readability and maintainability.
• Minor Script Fix: Corrected random.randint argument notation in tutobooks.py from 1e6 to 10**6 for improved clarity and precision.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[gemini-code-assist]

Code Review

This pull request adds a new section to the quantization overview guide, explaining how to use layer filters for selective quantization. The guide is updated across the notebook, markdown, and Python script formats. The changes are clear and the examples for regex and callable filters are helpful. Additionally, a critical bug in scripts/tutobooks.py is fixed, where random.randint was called with float arguments, which would cause a ValueError. I have one minor suggestion to improve the formatting of the generated notebook.

[gemini-code-assist]

This empty line between two consecutive docstring blocks will be interpreted as an empty code cell by the tutobooks.py script, resulting in an unnecessary empty cell in the generated Jupyter notebook. Please remove this empty line to avoid this.