Anatomy of a domain library

PyTorch Developer Podcast

コンテンツは PyTorch, Edward Yang, and Team PyTorch によって提供されます。エピソード、グラフィック、ポッドキャストの説明を含むすべてのポッドキャストコンテンツは、PyTorch, Edward Yang, and Team PyTorch またはそのポッドキャストプラットフォームパートナーによって直接アップロードされ、提供されます。誰かがあなたの著作物をあなたの許可なく使用していると思われる場合は、ここで概説されているプロセスに従うことができますhttps://ja.player.fm/legal。

4+ y ago 16:11

MP3•エピソードのホーム

What's a domain library? Why do they exist? What do they do for you? What should you know about developing in PyTorch main library versus in a domain library? How coupled are they with PyTorch as a whole? What's cool about working on domain libraries?

Further reading.

The classic trio of domain libraries is https://pytorch.org/audio/stable/index.html https://pytorch.org/text/stable/index.html and https://pytorch.org/vision/stable/index.html

Line notes.

why do domain libraries exist? lots of domains specific gadgets,
inappropriate for PyTorch
what does a domain library do
- operator implementations (old days: pure python, not anymore)
  - with autograd support and cuda acceleration
  - esp encoding/decoding, e.g., for domain file formats
    - torchbind for custom objects
    - takes care of getting the dependencies for you
  - esp transformations, e.g., for data augmentation
- models, esp pretrained weights
- datasets
- reference scripts
- full wheel/conda packaging like pytorch
- mobile compatibility
separate repos: external contributors with direct access
- manual sync to fbcode; a lot easier to land code! less
  motion so lower risk
coupling with pytorch? CI typically runs on nightlies
- pytorch itself tests against torchvision, canary against
  extensibility mechanisms
- mostly not using internal tools (e.g., TensorIterator),
  too unstable (this would be good to fix)
closer to research side of pytorch; francesco also part of papers

83 つのエピソード

#Tech #PyTorch #Edward Yang #Team PyTorch #Deep Learning #Machine Learning