Skip to content

Add Evo2 LoRA fine-tuning notebook#1567

Merged
balvisio merged 1 commit intomainfrom
dev/ba/BIO-467-evo2-lora-notebook
May 7, 2026
Merged

Add Evo2 LoRA fine-tuning notebook#1567
balvisio merged 1 commit intomainfrom
dev/ba/BIO-467-evo2-lora-notebook

Conversation

@balvisio
Copy link
Copy Markdown
Collaborator

@balvisio balvisio commented May 1, 2026

Description

Add Jupyter Notebook to demo LoRA fine-tuning of Evo2

Type of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactor
  • Documentation update
  • Other (please describe):

CI Pipeline Configuration

Configure CI behavior by applying the relevant labels. By default, only basic unit tests are run.

  • ciflow:skip - Skip all CI tests for this PR
  • ciflow:notebooks - Run Jupyter notebooks execution tests
  • ciflow:slow - Run slow single GPU integration tests marked as @pytest.mark.slow
  • ciflow:all - Run all tests (unit tests, slow tests, and notebooks). This label can be used to enforce running all framework tests.
  • ciflow:all-recipes - Run tests for all recipes (under bionemo-recipes). This label can be used to enforce running tests for all recipes.

Unit tests marked as @pytest.mark.multi_gpu or @pytest.mark.distributed are not run in the PR pipeline.

For more details, see CONTRIBUTING

Note

By default, only basic unit tests are run. Add appropriate labels to enable an additional test coverage.

Authorizing CI Runs

We use copy-pr-bot to manage authorization of CI
runs on NVIDIA's compute resources.

  • If a pull request is opened by a trusted user and contains only trusted changes, the pull request's code will
    automatically be copied to a pull-request/ prefixed branch in the source repository (e.g. pull-request/123)
  • If a pull request is opened by an untrusted user or contains untrusted changes, an NVIDIA org member must leave an
    /ok to test comment on the pull request to trigger CI. This will need to be done for each new commit.

Triggering Code Rabbit AI Review

To trigger a code review from code rabbit, comment on a pull request with one of these commands:

See https://docs.coderabbit.ai/reference/review-commands for a full list of commands.

Pre-submit Checklist

  • I have tested these changes locally
  • I have updated the documentation accordingly
  • I have added/updated tests as needed
  • All existing tests pass successfully

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 1, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 89bf330d-c97c-45e0-8859-7c7ad7baf227

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev/ba/BIO-467-evo2-lora-notebook

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Comment @coderabbitai help to get the list of available commands and usage tips.

@balvisio balvisio force-pushed the dev/ba/BIO-467-evo2-lora-notebook branch from 1e625f2 to 1b3f803 Compare May 1, 2026 10:18
@balvisio
Copy link
Copy Markdown
Collaborator Author

balvisio commented May 1, 2026

@jstjohn here is the Jupyter Notebook for Evo2 LoRA. Thanks.

Comment thread bionemo-recipes/recipes/evo2_megatron/README.md
@balvisio balvisio force-pushed the dev/ba/BIO-467-evo2-lora-notebook branch from 1b3f803 to 880dc33 Compare May 6, 2026 21:25
@balvisio balvisio added the ciflow:notebooks Run Jupyter notebooks execution tests for docs and bionemo2 label May 6, 2026
@balvisio balvisio force-pushed the dev/ba/BIO-467-evo2-lora-notebook branch 3 times, most recently from 098031b to a69101d Compare May 6, 2026 23:25
Signed-off-by: Bruno Alvisio <balvisio@nvidia.com>
@balvisio balvisio force-pushed the dev/ba/BIO-467-evo2-lora-notebook branch from a69101d to 41d744d Compare May 7, 2026 00:15
@balvisio balvisio added this pull request to the merge queue May 7, 2026
Merged via the queue into main with commit e870d31 May 7, 2026
23 checks passed
@balvisio balvisio deleted the dev/ba/BIO-467-evo2-lora-notebook branch May 7, 2026 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow:notebooks Run Jupyter notebooks execution tests for docs and bionemo2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants