Skip to content

Comments

Report Generation: Adding notebooks to better explain the usage#61

Merged
lotif merged 9 commits intomainfrom
marcelo/notebooks
Feb 19, 2026
Merged

Report Generation: Adding notebooks to better explain the usage#61
lotif merged 9 commits intomainfrom
marcelo/notebooks

Conversation

@lotif
Copy link
Collaborator

@lotif lotif commented Feb 19, 2026

Summary

Adding notebooks to better explain the usage and features of the Report Generation Agent. Also performing minor bug fixes.

Clickup Ticket(s): NA

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • 🧪 Test improvements
  • 🔒 Security fix

Changes Made

Adding three notebooks to:

  • Download and import the dataset into an SQLite DB
  • Run the agent with online evaluations
  • Run the offline evaluations

Also making a few adjustments and fixing a few bugs found while making the notebooks.

Testing

  • Tests pass locally (uv run pytest tests/)
  • Type checking passes (uv run mypy <src_dir>)
  • Linting passes (uv run ruff check src_dir/)
  • Manual testing performed (describe below)

Manual testing details:

Ran the notebooks and made sure they work.

Checklist

  • Code follows the project's style guidelines
  • Self-review of code completed
  • Documentation updated (if applicable)
  • No sensitive information (API keys, credentials) exposed

@lotif lotif requested review from amrit110 and fcogidi February 19, 2026 15:16
Copy link
Member

@amrit110 amrit110 left a comment

Choose a reason for hiding this comment

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

Just the one comment. The code itself looks good!

Copy link
Member

Choose a reason for hiding this comment

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

I'm generally not in favour of committing the outputs of cells. It just adds a lot more clutter to the git history, and usually it can change between runs as well. So consider clearing the outputs and only commit the code.

Copy link
Member

@amrit110 amrit110 left a comment

Choose a reason for hiding this comment

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

Just minor typos. Actually you could try adding this pre-commit hook and run ot once for all the notebooks:

https://github.com/VectorInstitute/aieng-template-uv/blob/main/.pre-commit-config.yaml#L45C1-L49C17

"\n",
"Offline evaluations are evaluations run against a **pre-defined dataset**. It performs **detailed evaluations** of the **outputs** of the agentic system and the **steps** it has taken to produce those evaluations.\n",
"\n",
"This dataset is called the **expected results** or the **ground-truth** dataset, and on this case it's a **handcrafted** dataset with **inputs, oputputs and trajectory** for a few known use cases.\n",
Copy link
Member

Choose a reason for hiding this comment

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

typo: outputs

"source": [
"## Running the Evaluations\n",
"\n",
"To run those two evaluatoirs against all of the ground-truth dataset samples, run the function below:"
Copy link
Member

Choose a reason for hiding this comment

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

typo: evaluator

@lotif
Copy link
Collaborator Author

lotif commented Feb 19, 2026

@amrit110 the precommit didn't work very well. It's picking up certifi (the package) as a typo and not looking into the notebooks. I'm gonna skip adding it for now.

@lotif lotif merged commit ad70681 into main Feb 19, 2026
3 checks passed
@lotif lotif deleted the marcelo/notebooks branch February 19, 2026 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants