flâneur

[D] Modern best coding practices for Pytorch (for research)? : r/MachineLearning

reddit.com · 687 words · saved by 1 readers

Beginners -> /r/mlquestions or /r/learnmachinelearning , AGI -> /r/singularity, career advices -> /r/cscareerquestions, datasets -> r/datasets Hi all, I've been using Pytorch since 2019, and it has changed a lot in that time (especially since huggingface). Are there any modern guides/style-docs/example-repos you would recommend? For example, are namedtensors a good/common practice? Is Pytorch Lightning recommended? What are the best config management tools these days? How often do you use torch.script or torch.compile? I really like the torchcfm library (it does flow matching) as an example of something modern and nontrivial that is none the less implemented in an extremely clean and well-organized way. I think there's a real need for something akin to namedtensors, in the sense that reading regular pytorch code often doesn't give clear indications about what the meaning or shape of tensors is expected to be. At the same time, though, I think the lack of enthusiastic adoption suggests

I really like the torchcfm library (it does flow matching) as an example of something modern and nontrivial that is none the less implemented in an extremely clean and well-organized way. I think there's a real need for something akin to namedtensors, in the sense that reading regular pytorch code often doesn't give clear indications about what the meaning or shape of tensors is expected to be. At the same time, though, I think the lack of enthusiastic adoption suggests that namedtensors don't really solve that problem; I think people have found it a lot easier to just remember various…

related reading