understanding the input format

[romainVala]

understanding the input format

[fepegar]

It's true that the function of the type value in the image dict is not clear from the examples. And yes, the type in the example should be LABEL.

For now, I mostly use the type to decide whether to apply or not a transform or to choose an interpolation mode. For example, RandomAffine is applied to all images, but if the type is LABEL, the interpolation is set to nearest neighbor. For some transforms like RandomMotion, the operation is only applied to INTENSITY images.

This value still needs some thinking. I also think that maybe I should define Subject and Image classes that can be used to populate the paths_list. Then the necessary keys can be checked more easily. What do you think?

[fepegar]

Example fixed in cca1830.

[romainVala]

Ok I see the point, and it makes more sense than the previous solution which was relying on the keywork name

About a Subject class, I am not sure if it is necessary. The ImgeDataset is taking as input a subject_list (which is self explicit)

So now it is the users duty to construct correctly this subject_list. Since it is so much dependent on how you organize your files, I will let it like that

By the way currently the RandomMotion is also applied to label and sampling map, (with different motions)

[fepegar]

Thanks for reporting that.

Maybe a Subject class is not necessary, but an Image one might be useful to validate that the path and type are correct. This format would be dropped when reading the file in ImagesDataset, so that only dicts are passed between transforms.