> For the complete documentation index, see [llms.txt](https://docs.valohai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valohai.com/project-gallery/computer-vision/nvidia-monai-valohai.md).

# Medical Imaging Segmentation with NVIDIA MONAI

***

### Overview

This example demonstrates how to:

* Preprocess medical imaging data
* Train a MONAI U-Net model
* Evaluate segmentation performance
* Run inference on new images

***

### Steps

{% stepper %}
{% step %}
**Preprocess Data**

Load and normalize medical imaging data.
{% endstep %}

{% step %}
**Train Model**

Initialize and train a MONAI U-Net model using your dataset.
{% endstep %}

{% step %}
**Evaluate Performance**

Assess the model's segmentation accuracy with test data.
{% endstep %}

{% step %}
**Run Inference**

Use the trained model to predict and segment new images.
{% endstep %}
{% endstepper %}

***

### GitHub repository

The repository walks you through how to go through the above steps:

{% embed url="<https://github.com/valohai/NVIDIA-MONAI-Valohai>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.valohai.com/project-gallery/computer-vision/nvidia-monai-valohai.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.