These are chat archives for thunder-project/thunder
tupelizefunction so that we always make sure the keys end up as tuples, no matter what
@rmchurch I can see the sc.parallelize... Would there be any reason that using loadImages() on a .tif stack with nplanes=1 would end up doing the def read in LocalFSFileReader? Basically when I reserve a node on our cluster, I take the whole node and all cores, run in local mode, and parallelize across the node. However, Thunder doesn't automatically parallelize my tif stack when I read it in in this method and I'm trying to figure out why.
It stays on one core until I do a .toSeries() to the data, then it will parallelize correctly.