Add environment infrastructure files

Signed-off-by: Benjamin <benjamin.plattner@ost.ch>

.devcontainer/devcontainer.json

+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/docker-existing-docker-compose
+{
+	"name": "GenAI Exercises",
+	"build": {
+		"context": "..",
+		"dockerfile": "../Dockerfile"
+	},
+
+	"features": {
+		"ghcr.io/devcontainers/features/common-utils:2": {
+			"installZsh": true,
+			"configureZshAsDefaultShell": true,
+			"installOhMyZsh": true,
+			"installOhMyZshConfig": true,
+			"upgradePackages": false,
+			"username": "mambauser",
+			"userUid": "1000",
+			"userGid": "1000"
+		}
+	},
+	"remoteUser": "mambauser",
+	"customizations": {
+		"vscode": {
+			"extensions": [
+				"ms-azuretools.vscode-docker",
+				"ms-python.python",
+				"ms-toolsai.jupyter",
+				"ms-python.vscode-pylance",
+				"streetsidesoftware.code-spell-checker",
+				"charliermarsh.ruff",
+				"ms-toolsai.tensorboard"
+			],
+			"settings": {
+				"[python]": {
+					"editor.defaultFormatter": "charliermarsh.ruff"
+				},
+				"ruff.path": ["/opt/conda/bin/ruff"],
+				"ruff.interpreter": ["/opt/conda/bin/python"],
+
+				// Ruler for "black"-formatted line widths
+				"editor.rulers": [88],
+
+				// Disable barely usable scrollbar
+				"workbench.editor.wrapTabs": true,
+
+				// Turn on autosave
+				"files.autoSave": "afterDelay",
+
+				// Show whitespace as tiny grey dots
+				"editor.renderWhitespace": "boundary",
+
+				// Use Pylance
+				"python.languageServer": "Pylance",
+				"python.analysis.typeCheckingMode": "basic",
+
+				// Interpret lines beginning with "# !%" as ipython magic commands
+				"jupyter.interactiveWindow.textEditor.magicCommandsAsComments": true,
+
+				// Path of the default Python environment
+				"python.defaultInterpreterPath": "/opt/conda/bin/python",
+
+				// Disable the "conda activate base" command when opening a new terminal
+				"python.terminal.activateEnvironment": false,
+
+				// Automatically keep Git up-to-date with remotes
+				"git.autofetch": "all",
+
+				// Make sure that key combos like Ctrl+K are not intercepted by VS Code
+				// when using the terminal
+				"terminal.integrated.allowChords": false
+			}
+		}
+	},
+
+	"postCreateCommand": {
+		"micromamba-activate": "echo 'eval \"$(micromamba shell hook --shell bash)\" && micromamba activate' >> ~/.zshrc",
+		"git-safe-dir": "echo 'git config --global --add safe.directory /workspaces/${localWorkspaceFolderBasename}' >> ~/.zshrc"
+	}
+	// do not remove the GPU comment, it is used by setup.sh
+	// GPU
+}

.gitignore

+.DS_Store
+__pycache__
+.env*
+*.wav
+*.h5
+*.keras
+model.png
+runs/
\ No newline at end of file

Dockerfile

+FROM mambaorg/micromamba:1.5.9
+
+ARG DEBIAN_FRONTEND=noninteractive
+ARG NEW_MAMBA_USER=${MAMBA_USER}
+ARG NEW_MAMBA_USER_ID=1000
+ARG NEW_MAMBA_USER_GID=1000
+
+USER root
+
+RUN if grep -q '^ID=alpine$' /etc/os-release; then \
+      # alpine does not have usermod/groupmod
+      apk add --no-cache --virtual temp-packages shadow; \
+    fi && \
+    usermod "--login=${NEW_MAMBA_USER}" "--home=/home/${NEW_MAMBA_USER}" \
+        --move-home "-u ${NEW_MAMBA_USER_ID}" "${MAMBA_USER}" && \
+    groupmod "--new-name=${NEW_MAMBA_USER}" \
+        "-g ${NEW_MAMBA_USER_GID}" "${MAMBA_USER}" && \
+    if grep -q '^ID=alpine$' /etc/os-release; then \
+      # remove the packages that were only needed for usermod/groupmod
+      apk del temp-packages; \
+    fi && \
+    echo "${NEW_MAMBA_USER}" > "/etc/arg_mamba_user" && \
+    : \
+    echo "deb https://deb.debian.org/debian bookworm main" > /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian-security bookworm-security main" >> /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian bookworm-updates main" >> /etc/apt/sources.list \
+    && apt-get update -qq \
+    && apt-get install -y --no-install-recommends apt-transport-https ca-certificates \
+    && apt-get update -qq \
+    && apt-get upgrade -y --no-install-recommends \
+    && apt-get install -y --no-install-recommends \
+        git gnupg2 ssh build-essential abcmidi timidity fluid-soundfont-gm \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* \
+    && rm -rf /var/cache/apt/archives/* /var/cache/apt/archives/partial/*
+
+USER ${MAMBA_USER}
+
+RUN --mount=type=bind,source=environment.yaml,target=/tmp/environment.yaml \ 
+    micromamba install -y -n base -f /tmp/environment.yaml \
+    && micromamba clean -afy

Dockerfile.cpu

+FROM mambaorg/micromamba:1.5.9
+
+ARG DEBIAN_FRONTEND=noninteractive
+ARG NEW_MAMBA_USER=${MAMBA_USER}
+ARG NEW_MAMBA_USER_ID=1000
+ARG NEW_MAMBA_USER_GID=1000
+
+USER root
+
+RUN if grep -q '^ID=alpine$' /etc/os-release; then \
+      # alpine does not have usermod/groupmod
+      apk add --no-cache --virtual temp-packages shadow; \
+    fi && \
+    usermod "--login=${NEW_MAMBA_USER}" "--home=/home/${NEW_MAMBA_USER}" \
+        --move-home "-u ${NEW_MAMBA_USER_ID}" "${MAMBA_USER}" && \
+    groupmod "--new-name=${NEW_MAMBA_USER}" \
+        "-g ${NEW_MAMBA_USER_GID}" "${MAMBA_USER}" && \
+    if grep -q '^ID=alpine$' /etc/os-release; then \
+      # remove the packages that were only needed for usermod/groupmod
+      apk del temp-packages; \
+    fi && \
+    echo "${NEW_MAMBA_USER}" > "/etc/arg_mamba_user" && \
+    : \
+    echo "deb https://deb.debian.org/debian bookworm main" > /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian-security bookworm-security main" >> /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian bookworm-updates main" >> /etc/apt/sources.list \
+    && apt-get update -qq \
+    && apt-get install -y --no-install-recommends apt-transport-https ca-certificates \
+    && apt-get update -qq \
+    && apt-get upgrade -y --no-install-recommends \
+    && apt-get install -y --no-install-recommends \
+        git gnupg2 ssh build-essential abcmidi timidity fluid-soundfont-gm \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* \
+    && rm -rf /var/cache/apt/archives/* /var/cache/apt/archives/partial/*
+
+USER ${MAMBA_USER}
+
+RUN --mount=type=bind,source=environment.yaml,target=/tmp/environment.yaml \ 
+    micromamba install -y -n base -f /tmp/environment.yaml \
+    && micromamba clean -afy

Dockerfile.gpu

+FROM mambaorg/micromamba:1.5.9
+
+ARG DEBIAN_FRONTEND=noninteractive
+ARG NEW_MAMBA_USER=${MAMBA_USER}
+ARG NEW_MAMBA_USER_ID=1000
+ARG NEW_MAMBA_USER_GID=1000
+
+USER root
+
+RUN if grep -q '^ID=alpine$' /etc/os-release; then \
+      # alpine does not have usermod/groupmod
+      apk add --no-cache --virtual temp-packages shadow; \
+    fi && \
+    usermod "--login=${NEW_MAMBA_USER}" "--home=/home/${NEW_MAMBA_USER}" \
+        --move-home "-u ${NEW_MAMBA_USER_ID}" "${MAMBA_USER}" && \
+    groupmod "--new-name=${NEW_MAMBA_USER}" \
+        "-g ${NEW_MAMBA_USER_GID}" "${MAMBA_USER}" && \
+    if grep -q '^ID=alpine$' /etc/os-release; then \
+      # remove the packages that were only needed for usermod/groupmod
+      apk del temp-packages; \
+    fi && \
+    echo "${NEW_MAMBA_USER}" > "/etc/arg_mamba_user" && \
+    : \
+    echo "deb https://deb.debian.org/debian bookworm main" > /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian-security bookworm-security main" >> /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian bookworm-updates main" >> /etc/apt/sources.list \
+    && apt-get update -qq \
+    && apt-get install -y --no-install-recommends apt-transport-https ca-certificates \
+    && apt-get update -qq \
+    && apt-get upgrade -y --no-install-recommends \
+    && apt-get install -y --no-install-recommends \
+        git gnupg2 ssh build-essential abcmidi timidity fluid-soundfont-gm \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* \
+    && rm -rf /var/cache/apt/archives/* /var/cache/apt/archives/partial/*
+
+USER ${MAMBA_USER}
+
+RUN --mount=type=bind,source=environment-gpu.yaml,target=/tmp/environment.yaml \ 
+    CONDA_OVERRIDE_CUDA=12.4 micromamba install -y -n base -f /tmp/environment.yaml \
+    && micromamba clean -afy

Dockerfile.mps

+FROM mambaorg/micromamba:1.5.9
+
+ARG DEBIAN_FRONTEND=noninteractive
+ARG NEW_MAMBA_USER=${MAMBA_USER}
+ARG NEW_MAMBA_USER_ID=1000
+ARG NEW_MAMBA_USER_GID=1000
+
+USER root
+
+RUN if grep -q '^ID=alpine$' /etc/os-release; then \
+      # alpine does not have usermod/groupmod
+      apk add --no-cache --virtual temp-packages shadow; \
+    fi && \
+    usermod "--login=${NEW_MAMBA_USER}" "--home=/home/${NEW_MAMBA_USER}" \
+        --move-home "-u ${NEW_MAMBA_USER_ID}" "${MAMBA_USER}" && \
+    groupmod "--new-name=${NEW_MAMBA_USER}" \
+        "-g ${NEW_MAMBA_USER_GID}" "${MAMBA_USER}" && \
+    if grep -q '^ID=alpine$' /etc/os-release; then \
+      # remove the packages that were only needed for usermod/groupmod
+      apk del temp-packages; \
+    fi && \
+    echo "${NEW_MAMBA_USER}" > "/etc/arg_mamba_user" && \
+    : \
+    echo "deb https://deb.debian.org/debian bookworm main" > /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian-security bookworm-security main" >> /etc/apt/sources.list \
+    && echo "deb https://deb.debian.org/debian bookworm-updates main" >> /etc/apt/sources.list \
+    && apt-get update -qq \
+    && apt-get install -y --no-install-recommends apt-transport-https ca-certificates \
+    && apt-get update -qq \
+    && apt-get upgrade -y --no-install-recommends \
+    && apt-get install -y --no-install-recommends \
+        git gnupg2 ssh build-essential abcmidi timidity fluid-soundfont-gm \
+    && apt-get clean \
+    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* \
+    && rm -rf /var/cache/apt/archives/* /var/cache/apt/archives/partial/*
+
+USER ${MAMBA_USER}
+
+RUN --mount=type=bind,source=environment-mps.yaml,target=/tmp/environment.yaml \ 
+    micromamba install -y -n base -f /tmp/environment.yaml \
+    && micromamba clean -afy

README.md

-# Exercises
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.ost.ch/generative-ai/student-space/exercises.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.ost.ch/generative-ai/student-space/exercises/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+# Generative AI Exercises Repository
+
+> Please **read and follow** the below instructions carefully. Ask for help if you get stuck.
+
+## 1. Fork this repository
+
+By forking this repository you can keep your changes while pulling new content that is regularly pushed to the original repository.
+
+1. **Fork**
+    1. On the top-right, click on the `Fork` button
+    1. In the `select namespace` field, enter your `first.lastname`
+    1. (optional) Modify the `project slug` name to e.g., *gen-ai-24-exercises*
+    1. Select `All Branches`
+    1. Change the visibility to `Private` if you do not want your modifications to be public
+    1. Click on `Fork project`
+    1. You should see a message saying: **The project was successfully forked.**
+1. **Clone**
+    1. Clone the project to your machine, ideally using *SSH*
+    1. Go into the cloned project `cd <project name>`
+    1. By executing `git remote -v` you should see two entries starting with `origin`
+    1. Add the original repository to fetch updates from:
+        - SSH: `git remote add upstream ssh://git@gitlab.ost.ch:45022/generative-ai/student-space/exercises.git`
+        - (alternatively) HTTPS: `git remote add upstream https://gitlab.ost.ch/generative-ai/student-space/exercises.git`
+    1. Run `git remote -v` again and you should get four entries, two named `origin` and two named `upstream`
+    1. Run `git fetch upstream main` to fetch the main branch of the original repository
+1. **Branches** (optional)
+    1. Consider creating branches when you work on an exercise: `git checkout -b <branch-name>`
+    1. Rebase frequently to avoid or reduce merge conflicts:
+        1. `git fetch upstream`
+        1. `git rebase upstream/main`
+    1. Merge your changes back into main
+        1. `git checkout main`
+        1. `git merge <branch-name>`
+1. **Updates**
+    1. Commit or stash your local changes
+    1. To pull the new exercises, execute `git pull upstream main`
+
+## 2. Setup
+
+### Option 1 - Dev Container (preferred)
+
+Activate the appropriate environment for your machine (GPU if available, MPS or CPU otherwise):
+1. Run the [./setup.sh](setup.sh) (Linux, macOS) or [\.setup.ps1](setup.ps1) (Windows) script
+(it switches the Dockerfile that installs the GPU versions of PyTorch and tensorflow and adds GPU access by the Dev Container)
+1. Open the repository in VS Code
+1. VS Code should ask you to open the repository as a Dev Container.
+    1. If you are not asked, hit `Ctrl+Shift+P` (Windows, Linux) or `Cmd+Shift+P` (macOS) and type & select
+    `Dev Containers: Reopen in Container`
+1. The first time it will take about 5-10 minutes to download the image and install all dependencies.
+1. Afterwards, the startup should take only a few seconds.
+1. Hit `` Ctrl+Shift+` `` or select `Terminal` -> `New Terminal` from the menu.
+1. Your Conda environment should automatically be activated (you should see `(base)` at the beginning of every line in your console).
+
+### Option 2 - Python venv
+
+1. Create a virtual environment within the forked repository: `python -m venv venv`
+1. Activate the venv: `source venv/bin/activate` (macOS, Linux) or `venv\Scripts\activate` (Windows)
+1. Install the dependencies using `pip install -r requirements.txt`.
+1. Launch your Jupyter notebook server using `jupyter lab`.
+
+## 3. Add a package (if needed)
+
+There are two approaches:
+- **Temporary**: the below commands only install the package locally; it persists during a restart, but not during a rebuild.
+- **Persistent**: this action below persists packages during rebuilds of the Dev Container.
+
+### Micromamba / Conda-forge
+1. Ensure that your folder is opened in the Dev Container.
+1. **Temporary**: Replace `<package>` with one or more packages `micromamba install <package> -c conda-forge`.
+1. **Persistent**: Add a line with the new package to `environment.yaml`, `environment-gpu.yaml`, or `environment-mps.yaml` depending on your machine.
+
+### pip (Conda)
+1. Ensure that your folder is opened in the Dev Container.
+1. **Temporary**: Run `pip install <package>`.
+1. **Persistent**: Add a line with `- <package>` below the section `- pip:` in the `environment.yaml` (or `-gpu/-mps.yaml`).
+
+### pip (venv)
+1. Ensure that you are within the virtual environment
+1. **Temporary**: Run `pip install <package>`.
+1. **Persistent**: Add the `<package>` to the `requirements.txt`.
\ No newline at end of file

environment-gpu.yaml

+name: base
+channels:
+  - conda-forge
+  - pytorch
+  - nvidia
+dependencies:
+  - python=3.11
+  - pip=24.2
+  - ipykernel=6.29.5
+  - ipywidgets=8.1.5
+  - matplotlib=3.9.2
+  - ruff=0.6.4
+  - scipy=1.14.1
+  - regex=2024.7.24
+  - tqdm=4.66.5
+  - pydot=3.0.1  # required to plot model architecture
+  - ipympl=0.9.4  # required for %matplotlib widget
+  - scikit-learn=1.5.1
+  - tensorflow-gpu=2.17.0
+  - keras=3.5.0
+  - pytorch::pytorch=2.4.1
+  - pytorch::pytorch-cuda=12.4
\ No newline at end of file

environment-mps.yaml

+name: base
+channels:
+  - conda-forge
+  - pytorch
+dependencies:
+  - python=3.11
+  - pip=24.2
+  - ipykernel=6.29.5
+  - ipywidgets=8.1.5
+  - matplotlib=3.9.2
+  - ruff=0.6.4
+  - scipy=1.14.1
+  - regex=2024.7.24
+  - tqdm=4.66.5
+  - pydot=3.0.1  # required to plot model architecture
+  - ipympl=0.9.4  # required for %matplotlib widget
+  - scikit-learn=1.5.1
+  - h5py=3.11.0  # required for keras and tf via pip
+
+  - pip:
+    - tensorflow==2.17.0
+    - keras==3.5.0
+    - torch==2.4.1
\ No newline at end of file

environment.yaml

+name: base
+channels:
+  - conda-forge
+  - pytorch
+dependencies:
+  - python=3.11
+  - pip=24.2
+  - ipykernel=6.29.5
+  - ipywidgets=8.1.5
+  - matplotlib=3.9.2
+  - ruff=0.6.4
+  - scipy=1.14.1
+  - regex=2024.7.24
+  - tqdm=4.66.5
+  - pydot=3.0.1  # required to plot model architecture
+  - ipympl=0.9.4  # required for %matplotlib widget
+  - scikit-learn=1.5.1
+  - tensorflow=2.17.0
+  - keras=3.5.0
+  - pytorch::pytorch=2.4.1
+  - pytorch::cpuonly=2.0
\ No newline at end of file

requirements.txt

+ipykernel==6.29.5
+ipywidgets==8.1.5
+matplotlib==3.9.2
+ruff==0.6.4
+scipy==1.14.1
+regex==2024.7.24
+tqdm==4.66.5
+pydot==3.0.1  # required to plot model architecture
+ipympl==0.9.4  # required for %matplotlib widget
+scikit-learn==1.5.1
+tensorflow==2.17.0
+keras==3.5.0
+torch==2.4.1
\ No newline at end of file

setup.ps1

+# Define the GPU comment
+$GPU_COMMENT = "// GPU"
+
+# Check if NVIDIA GPU is available
+if (Get-Command nvidia-smi -ErrorAction SilentlyContinue) {
+    # Copy Dockerfile.gpu to Dockerfile
+    Copy-Item -Path "Dockerfile.gpu" -Destination "Dockerfile"
+
+    # Read the content of devcontainer.json
+    $devcontainerJsonPath = ".devcontainer/devcontainer.json"
+    $devcontainerContent = Get-Content -Path $devcontainerJsonPath -Raw
+
+    # Check if the GPU comment exists in the file
+    if ($devcontainerContent -match [regex]::Escape($GPU_COMMENT)) {
+        # Replace the GPU comment with the required runArgs
+        $updatedContent = $devcontainerContent -replace [regex]::Escape($GPU_COMMENT), ',"runArgs": ["--gpus", "all"]'
+        Set-Content -Path $devcontainerJsonPath -Value $updatedContent
+        Write-Output "GPU setup complete"
+    } else {
+        Write-Output "Error: Comment '$GPU_COMMENT' not found in devcontainer.json => you should add it before the last '}'."
+        exit 1
+    }
+} else {
+    # Copy Dockerfile.cpu to Dockerfile
+    Copy-Item -Path "Dockerfile.cpu" -Destination "Dockerfile"
+    Write-Output "No GPU found, running on CPU"
+}
\ No newline at end of file

setup.sh

+#!/bin/bash
+GPU_COMMENT="// GPU"
+arch=$(uname -m)
+os=$(uname -s)
+
+if nvidia-smi > /dev/null 2>&1; then
+  cp Dockerfile.gpu Dockerfile
+  if grep -q "$GPU_COMMENT" .devcontainer/devcontainer.json; then
+    sed -i "s|$GPU_COMMENT|,\"runArgs\": [\"--gpus\", \"all\"]|" .devcontainer/devcontainer.json
+    echo "GPU setup complete"
+  else
+    echo "Error: Comment \"$GPU_COMMENT\" not found in devcontainer.json => you should add it before the last \"}\"."
+    exit 1
+  fi
+elif [ "$arch" == "arm64" ] && [ "$os" == "Darwin" ]; then
+  cp Dockerfile.mps Dockerfile
+  echo "ARM-based macOS detected, using MPS for GPU acceleration"
+else
+  cp Dockerfile.cpu Dockerfile
+  echo "No GPU found, running on CPU"
+fi