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
<
8000
div class="flash flash-full {{ className }}">
When training a model through the GUI, the preprocessing configuration sets the pad_to_stride parameter to a default value of 16. However, this value should ideally match the max_stride specified in the model configuration to ensure alignment. Currently, pad_to_stride is only updated to max_stride if it is explicitly set to None here
Since the GUI always defaults to 16, this override does not occur—even when a different max_stride is required—potentially leading to inconsistencies during training.
Expected behaviour
pad_to_stride should automatically match max_stride from the model config unless explicitly set.
Actual behaviour
The GUI always sets pad_to_stride to 16, leading to mis-alignment with max_stride.
Bug description
When training a model through the GUI, the preprocessing configuration sets the
pad_to_stride
parameter to a default value of 16. However, this value should ideally match themax_stride
specified in the model configuration to ensure alignment. Currently,pad_to_stride
is only updated tomax_stride
if it is explicitly set toNone
heresleap/sleap/nn/training.py
Lines 1021 to 1023 in 8228cd2
Since the GUI always defaults to 16, this override does not occur—even when a different
max_stride
is required—potentially leading to inconsistencies during training.Expected behaviour
pad_to_stride
should automatically matchmax_stride
from the model config unless explicitly set.Actual behaviour
The GUI always sets
pad_to_stride
to 16, leading to mis-alignment withmax_stride
.Your personal set up
Environment packages
Logs
Screenshots
How to reproduce
The text was updated successfully, but these errors were encountered: