From 632fa59ac7a7d669e95c57829ba35781a67719a9 Mon Sep 17 00:00:00 2001 From: Giordon Stark Date: Wed, 18 Mar 2026 09:50:57 -0600 Subject: [PATCH 1/2] add mlcpu --- docs/uchicago/jupyter.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/uchicago/jupyter.md b/docs/uchicago/jupyter.md index 9020baa..f2b1d36 100644 --- a/docs/uchicago/jupyter.md +++ b/docs/uchicago/jupyter.md @@ -71,7 +71,7 @@ documentation, see the You can install additional packages directly from your notebook with [`pixi`](https://pixi.prefix.dev/latest/). The `ml_platform` image organizes packages under features. For ML-related packages, use the `ml` feature (`-f ml`) -and install them with the `ml` environment (`-e ml`). +and install them with the `ml` environment (`-e ml`). If you are not using a GPU-node, you can use the `mlcpu` environment which has the same set of packages without the `cuda` system requirement. **Example**: installing the GPU-version of `pytorch` along with `torchvision` and `xgboost` available on [conda-forge](https://conda-forge.org/packages/), you @@ -274,16 +274,16 @@ pixi install -e my-env Choose the right approach for your needs to keep your environments manageable and maintainable: -**When to use the simple approach** (add to `ml` feature): +**When to use the simple approach** (add to `ml` or `mlcpu` feature): - You need just a few additional packages -- Packages are compatible with the existing `ml` environment +- Packages are compatible with the existing `ml` or `mlcpu` environment - You're doing exploratory work or quick prototyping - You don't need strict version control **When to create a custom environment:** -- You need specific package versions that conflict with `ml` +- You need specific package versions that conflict with `ml` or `mlcpu` - You're working on a long-term project with specific dependencies - You want to isolate different projects from each other - You're collaborating and need reproducible environments From 19e30cee76c408685fbb14bf464fb9414533d05b Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Wed, 18 Mar 2026 15:51:34 +0000 Subject: [PATCH 2/2] style: pre-commit fixes --- docs/uchicago/jupyter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/uchicago/jupyter.md b/docs/uchicago/jupyter.md index f2b1d36..fbb3695 100644 --- a/docs/uchicago/jupyter.md +++ b/docs/uchicago/jupyter.md @@ -71,7 +71,9 @@ documentation, see the You can install additional packages directly from your notebook with [`pixi`](https://pixi.prefix.dev/latest/). The `ml_platform` image organizes packages under features. For ML-related packages, use the `ml` feature (`-f ml`) -and install them with the `ml` environment (`-e ml`). If you are not using a GPU-node, you can use the `mlcpu` environment which has the same set of packages without the `cuda` system requirement. +and install them with the `ml` environment (`-e ml`). If you are not using a +GPU-node, you can use the `mlcpu` environment which has the same set of packages +without the `cuda` system requirement. **Example**: installing the GPU-version of `pytorch` along with `torchvision` and `xgboost` available on [conda-forge](https://conda-forge.org/packages/), you