Viewing a single comment thread. View all comments

shahaff32 t1_jbu0zmr wrote

In our research we ran into issues with Lightning. It is especially annoying when designing non-trivial layers or optimizers. Also, it is much harder to convert the code back to pure pytorch.

For example, in a recent peoject, Lightning caused each forward-backward to operate twice on each batch because we used a combination of two optimizers for a specific reason. And now we are working on rewriting everything without Lightning.

14

ghostfuckbuddy t1_jbwobij wrote

That just sounds like a bug. It might take a lot less effort to report it for patching than rewrite all your own code.

2

shahaff32 t1_jbxy6vj wrote

It might be a bug, and it might also be the case that we are the "idiot users" that don't get how to use the package correctly.

Either way, we decided to continue without Lightning (because of that reason and a few others), and therefore we need the code in pure PyTorch for future works that rely on it.

5