ImageData should take the image in the constructor

[fzimmermann89]

InhomCorr/src/inhomcorr/interfaces/mr_data_interface.py

Line 67 in 90c0b7a

def __init__(self) -> None:

I believe it would be usefuull to just be able to set the image in the constructor. There are lots of places were we otherwise have the sequence of

img=ImageData()
img.data=image

I would even go so far to have the image mandatory in the init. Soi we never have an imageData that does not have an image tensor.

[ckolbPTB]

I agree or can anyone think of a use case where an empty ImageData object would be required?

[schuenke]

I also vote for including the image in the constructor. I cannot think of any case where we need an empty object. However, having the option to change the image data later makes sense imo.

[schuenke]

For ImageData we decided to enforce data in the constructor.
For QMRI:
def init(self, t1=None,rho=None, ...)
(some logic)
--> you can provide maps in the constructor. If you do, the shapes will be checked. If you don't, shape will be (1,1) implicitly.

[schote]

I agree or can anyone think of a use case where an empty ImageData object would be required?

Potentially, you could have an Image object which only contains the mask from the MRData class?