News for hackers. Stuff that matters.
Re:PyTorch 1.5 by jamisteven on Wednesday April 22, 2020 @05:24AM (#22943697)
Checkout PyTorch lightning.
Re:PyTorch 1.5 by sytelus on Wednesday April 22, 2020 @05:43AM (#22943823)
I want to love PyTorch lightning but like many other wrapper frameworks it also has severe problem: You can't use your dataloaders and nn.Module model as-is. FastAI also invents its own data bunch, dynamically specified models etc. All these reduces lines of code but then you are forced to adapt whole world to your new language.
Re:PyTorch 1.5 by JPKab on Wednesday April 22, 2020 @10:36PM (#22952331)
Fastai data bunch objects, along with all it's other data wrapper objects are incredibly simple. You can basically take any iterable and use it within them.
Re:PyTorch 1.5 by _lpa_ on Wednesday April 22, 2020 @07:11AM (#22944323)
Can't you? I have just been using the lightning class as a wrapper, with my normal model on self.model or something like this. Same for the dataloaders.
Re:PyTorch 1.5 by Y_Y on Wednesday April 22, 2020 @05:36AM (#22943777)
Seconded. It feels like cheating but it takes out a lot of boilerplate.

Overall pytorch is a product of suspiciously high quality. I would say "except for libtorch" but it looks like they might have remedied that in this release.

Re:PyTorch 1.5 by shafte on Thursday April 23, 2020 @02:23AM (#22953343)
I'm curious: what's sorts of things were bad about libtorch? What did you see in this release that you thought was an improvment?
Re:PyTorch 1.5 by JPKab on Wednesday April 22, 2020 @10:37PM (#22952335)
Seriously.

I'm on a debate with a teammate who is advocating for tensorflow. It doesn't even feel fair.