[Multi-Quant] follow-up to README and example

[brian-dellabetta]

SUMMARY:

• Add multi-quant information to top-level README
• Add --independent flag to example so both sequential and independent pipelines can be run in automated testing

TEST PLAN:
Example runs, freshly uploaded model checkpoint here

[github-actions]

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

[gemini-code-assist]

Summary of Changes

Hello @brian-dellabetta, 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 refines the documentation and usability of the multi-quantization feature. It introduces a new highlight in the top-level README to inform users about mixed-precision quantization and updates an example to enable seamless switching between sequential and independent quantization pipelines using a command-line flag, facilitating easier testing and exploration of this advanced functionality.

Highlights

• Documentation Update: The main README.md now includes a new entry highlighting the "Quantization with Multiple Modifiers" feature, detailing its capability for mixed-precision quantization.
• Example Documentation Clarification: The examples/quantization_non_uniform/README.md has been updated to clarify how to run independent multi-quantization pipelines, now instructing users to use a --independent command-line flag instead of modifying the oneshot function call directly.
• Example Script Enhancement: The quantization_multiple_modifiers.py example script has been enhanced to support a new --independent command-line argument, allowing users to easily switch between sequential and independent quantization pipelines for testing.

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

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 is a good follow-up for the multi-quantization feature. It introduces a command-line flag --independent to the example script, making it easier to switch between sequential and independent quantization pipelines. The documentation in the main README.md and the example's README.md has been updated accordingly to reflect this change and to better advertise the feature. The implementation is clean and straightforward. I have one suggestion to improve the structure of the example script for better maintainability.

[fynnsu]

Looks good!