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
Description:
The image illustrating the batching process for the FashionMNIST dataset appears to contain an error in the indexing of batch samples. Currently, the image displays the batch indices from 0 to 32, but it would be more accurate to display from 0 to 31, given that batch indices typically start at 0 and end at batch_size - 1.
Steps to Reproduce:
Refer to the attached image illustrating the FashionMNIST batching process.
Observe the batch sample indices listed at the top of the image samples, particularly the rightmost index.
Expected Behavior:
The batch indices should be labeled from 0 to 31 to accurately reflect a batch size of 32.
Actual Behavior:
The batch indices are labeled from 0 to 32.
Image:
Additional Information:
Correcting this labeling will help avoid any potential confusion for users trying to understand the batching process and the indexing of samples within a batch.
Thank you for your attention to this detail.
The text was updated successfully, but these errors were encountered:
Description:
The image illustrating the batching process for the FashionMNIST dataset appears to contain an error in the indexing of batch samples. Currently, the image displays the batch indices from 0 to 32, but it would be more accurate to display from 0 to 31, given that batch indices typically start at 0 and end at batch_size - 1.
Steps to Reproduce:
Expected Behavior:
The batch indices should be labeled from 0 to 31 to accurately reflect a batch size of 32.
Actual Behavior:
The batch indices are labeled from 0 to 32.
Image:
Additional Information:
Correcting this labeling will help avoid any potential confusion for users trying to understand the batching process and the indexing of samples within a batch.
Thank you for your attention to this detail.
The text was updated successfully, but these errors were encountered: