Queue is not respecting the batch size

[icekang]

Is there an existing issue for this?

• I have searched the existing issues

Bug summary

From the example, on the website, I have printed out the shape of patches_batch, its batch size is not the expected / specified value assigned to the data loader

Code for reproduction

# from https://torchio.readthedocs.io/patches/patch_training.html#queue
import torch
import torchio as tio
from torch.utils.data import DataLoader
patch_size = 96
queue_length = 300
samples_per_volume = 10
sampler = tio.data.UniformSampler(patch_size)
subject = tio.datasets.Colin27()
subjects_dataset = tio.SubjectsDataset(10 * [subject])
patches_queue = tio.Queue(
    subjects_dataset,
    queue_length,
    samples_per_volume,
    sampler,
    num_workers=4,
)
patches_loader = DataLoader(
    patches_queue,
    batch_size=16,
    num_workers=0,  # this must be 0
)
num_epochs = 2
model = torch.nn.Identity()
for epoch_index in range(num_epochs):
    for patches_batch in patches_loader:
        inputs = patches_batch['t1'][tio.DATA]  # key 't1' is in subject
        targets = patches_batch['brain'][tio.DATA]  # key 'brain' is in subject
        logits = model(inputs)  # model being an instance of torch.nn.Module

print(patches_batch['t1'][tio.DATA].shape, patches_batch['brain'][tio.DATA].shape)

Actual outcome

(torch.Size([4, 1, 96, 96, 96]), torch.Size([4, 1, 96, 96, 96]))

Error messages

No response

Expected outcome

(torch.Size([16, 1, 96, 96, 96]), torch.Size([16, 1, 96, 96, 96]))

System info

Platform:   Linux-6.5.0-35-generic-x86_64-with-glibc2.35
TorchIO:    0.19.6
PyTorch:    2.3.0+cu118
SimpleITK:  2.3.1 (ITK 5.3)
NumPy:      1.26.4
Python:     3.9.19 (main, May  6 2024, 19:43:03) 
[GCC 11.2.0]

[fepegar]

Can you please explain what happened?

…

On Tue, 28 May 2024 at 15:59, Naravich Chutisilp ***@***.***> wrote: Closed #1173 <#1173> as completed. — Reply to this email directly, view it on GitHub <#1173> or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAZVVAVRQ5O7Y3NEKPDGCDZESLVZBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLKRRGY4TQOBQGM2TINNENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWSHI4TVMWSG4YLNMWXHOYLUMNUF6YLDORUXM2LUPGWHG5LCNJSWG5C7OR4XAZNFJFZXG5LFUZ2G64DJMNZZHAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTEMRUGE2DQNZTHCBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGIZTEMJSHEYTEMBVQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRRGY4TQOBQGM2TINNHORZGSZ3HMVZKMY3MN5ZWKZA> . You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .