FrothyDog40 ,ClearML tries to conserve storage by limiting the history length for debug images (see sdk.metrics.file_history_size configuration entry), though the history can indeed grow large by setting a large value or using a metric/variant naming scheme to circumvent this limit.I am aware, but I am not sure what did you try to say by thisDoes your use case call for accessing a specific iteration for all images or when looking at a specific image?Yes, for some cases I would like to access a specific iteration.Note that the debug image viewer (when you click a debug image) provides an iteration scroll control which allows quickly moving across the entire available iteration range for that image.I am familiar with it, however some debug images are not reported every iteration, and can be triggered according to some event. In that case I can' access the iteration scroll..
Other then having the option to choose arbitrary iteration, a filter similar to one in the scalars page where you can display a subset of the reported debug images can be useful
