> For the complete documentation index, see [llms.txt](https://docs.binaexperts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.binaexperts.com/train/advanced-hyperparameter/validation-input-image-size.md).

# Validation input image size

The validation input image size should ideally match the input size used during training to ensure consistency and comparability in the evaluation process. This means that the validation images should be resized or cropped to the same dimensions as the training images before being fed into the model for evaluation.

Maintaining consistency in input image sizes between training and validation is important because:

1. **Model Compatibility**: Neural network models are typically designed to accept input images of a specific size. Using different sizes during training and validation may result in incompatible input dimensions, leading to errors or unexpected behavior.
2. **Evaluation Consistency**: Evaluating the model's performance on validation data that differs in size from the training data may not provide an accurate representation of its true performance. Consistent input sizes ensure that the model is evaluated under the same conditions as during training.
3. **Fair Comparison**: Consistent input sizes enable fair comparisons between different models or configurations. If different models are trained with different input sizes, their performance cannot be directly compared without accounting for this difference.

To ensure consistency, it's recommended to preprocess the validation images to match the input size used during training. This may involve resizing, cropping, or padding the images as necessary. Additionally, it's important to document the preprocessing steps and input sizes used during both training and validation to ensure transparency and reproducibility in the evaluation process.


---

# 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.binaexperts.com/train/advanced-hyperparameter/validation-input-image-size.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.