You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MIN_SIZE_TRAIN: (800, 900, 1000, 1100, 1200) # resizing the shorter edge (randomly pick some value)
MAX_SIZE_TRAIN: 1999 # adjusting the longer edge. ensuring that the maximum edge of an processed image would not exceed 1999
These 2 lines represent the process of resizing the raw image to resized image, ensures that the aspect ratio of the image is maintained.
why ?:
Resizing an image in one step without considering the aspect ratio could distort the image. This is because the height and width of the image could be scaled by different factors, causing the objects in the image to appear stretched or squished. This distortion could negatively impact the performance of the model, as the features learned during training may not accurately represent the objects in the distorted image.
Answer to your two questions:
1. How does the detector handle variable input sizes?
Those two lines of code in your configuration are only the first step in ensuring that when you resize an image in your model pipeline, the aspect ratio of the input image is maintained. (training phase)
In inference phases, these two lines might not be needed.
2. Imagine the input image is (850, 950). How does a detector resize this image and proceed with it in the network?
resized the shorter edge (850) to some random value in your MIN_SIZE_TRAIN: (800, 900, 1000, 1100, 1200)
Checking the longer edge In this case, there is no need to adjust anything.
passing your processed image to the model pipeline
hello
what does this line in the config file mean?
MIN_SIZE_TRAIN: (800, 900, 1000, 1100, 1200)
MAX_SIZE_TRAIN: 1999
thank you
The text was updated successfully, but these errors were encountered: