adding PTQ recipe

[AnnaGutowska]

PR Checklist

Model Interaction

• [ ] Flexible LLM platform support The platform should be easily switchable. Use LangChain or LlamaIndex.
• [ ] Use prompt guide corresponding to the model For example for Granite 3.x Language Models

Data

• [ ] Example data: Follow the example data guidance.

Notebook requirements

• [x] Notebook outputs cleared: Ensure all notebook outputs are cleared.
• [x] Automated testing: Add the recipe to the automated tests as described here
• [ ] Test in Google Colab:
  • [ ] Test that it works in Google Colab (Python 3.10.12).
  • [ ] Colab has its own package set and Python version, so ensure compatibility.
• [x] Test locally:
  • [x] Ensure the code works in a fresh Python virtual environment (venv).
• [ ] Standard access to secrets and variables Include !pip install git+https://github.com/ibm-granite-community/utils in the first code cell in order to make get_env_var available to accessing secrets and variables in the recipe.

Incoming References

• [x] README.md updates:
  • [x] Add a link to the recipe in the Table of Contents (ToC).
  • [ ] Include a Colab button after that link.

GitHub

• [x] Commits signed: All commits must be GPG or SSH signed.
• [x] DCO Compliance: Developer Certificate of Origin (DCO) applies to the code, documentation, and any example data provided. Ensure commits are signed off.

[AnnaGutowska]

This recipe is in markdown format as the commands are run through the terminal. Since some tests are failing due to the file not being in notebook format, should I remove it from tests? Looking for guidance on adding this recipe, thanks!

[bjhargrave]

The notebooks list files assume all entries are Jupyter notebooks for testing purposes. So if this recipe it not a notebook, it must not me listed in a notebooks list file.

[adampingel]

@AnnaGutowska Can we not make this a notebook? Recipes in these repos are notebooks