Skip to content

non-Cartesian using batch size > 2 #13

Description

@yongwanlim

Hi Jon,

In deepinpy/deepinpy/forwards/mcmri/mcmri.py after line 82, I got an issue when using batch size > 2 for a non-Cartesian case.

I am not sure if this is only my problem but I found a workaround as follow:

else: 
     out_list = []
     out_list.append(out0)
     for i in range(1, batch_size):
          out_list.append(self.Aop_adjoint_list[i](x[i]))
     out = torch.stack(out_list, dim=0)'
     return out

And if I use batch size >> 1, the gradient seems to be exploding... I found the loss function defined as self._loss_fun = torch.nn.MSELoss(reduction='sum') in deepinpy/deepinpy/recons/recon.py. I was wondering if the loss function should be normalized by the batch size so that the actual learning rate is kept consistent with different batch sizes?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions