Re:PyTorch 2.0
by PartiallyTyped on Friday December 02, 2022 @06:18PM
(#33838299)
I found that there still some limitations with functorch's vmap, but I can't recall what it was.
Re:PyTorch 2.0
by carbocation on Friday December 02, 2022 @06:22PM
(#33838332)
Probably not your issue, but one kind of annoying bit is that the inputs need to be tensors. I ended up calling partial on the function I was messing around with and then vmapping the partial, which seemed to work.
Re:PyTorch 2.0
by PartiallyTyped on Saturday December 03, 2022 @08:17AM
(#33843235)
Pretty similar actually, I needed to pass in some parameters as tuples, lists, etc. Partial would have probably worked, but tbh I wasn't in the mood to try harder at 2am.
You probably were not doing anything wrong. I spent a lot of time trying to be clever in order to parallelize things like this and it just wasn't possible without doing CUDA extensions. But it is now! PyTorch now has vmap through functorch and it works.