Two data loaders for synthetic images about climategan HOT 3 CLOSED

Maybe the correct answer is whatever is easier to implement/modify haha

from climategan.

haha that's a good answer :p

so I guess I atomized data loaders in order to make things as flexible as possible w.r.t. data presence/absence (r|s, n|f, auxilliary tasks data) etc.

I agree it however does not allow for pairs and that the solution to have one single sim dataloader would make mores sense.

I'm not however convinced it would not induce a lot of complexity: a good thing with symmetry is that we can always do for loops etc. and avoid wild ifs that we might forget and that would break things...

So I'll say this: I'm fine with a single data loader as long as the overall multi_domain_batch data structure is the same

from climategan.

does that make sense to you @51N84D ?

from climategan.