Experiment tracker purpose-built for foundation model training.
We tweet about #LLM best practices & other cool stuff.
Read our blog at neptune.ai/blog
We have a treat for all @PyTorch users out there!
"8 Creators and Core Contributors Talk About Their Model Training Libraries From PyTorch Ecosystem"
First-hand info about:
- Philosophy
- Build-in features
- Extension capabilities
- and way more
bit.ly/32uKJx7
Just updated the @fastdotai integration with @NeptuneML so that you can have your experiments tracked, hosted and ready to share with others.
Check out the blog post about it bit.ly/2vcJJxI
Want to understand with code how to build #BERT?
Check this article!
@nielspace07 uses @pytorch and breaks the process into 4 sections:
- Preprocessing
- Building model
- Loss and Optimization
- Training
bit.ly/3fCuG8u
Good news! We integrated Neptune with another awesome library - Keras Tuner.
You can now:
-see charts of logged metrics
-see the parameters tried
-log hyperparameter search space
And more!
Docs 👉 bit.ly/2Yfp9eC
Thanks @fchollet and the team for this great library 🙏
#ToolAlert
dabl: an awesome library by @amuellerml that reduces boilerplate when creating baseline ML solutions.
With (dabl.) clean, plot, AnyClassifier, and explain you can do pretty much everything you need with a one-liner.
Check it out: amueller.github.io/dabl/dev/quick…
If you're training deep learning models, @fastdotai should definitely be your tool.
And if you want to additionally monitor your training (believe us, you should want that), try Neptune-fastai integration. It's just one additional callback.
Docs: bit.ly/38iUByG
Before creating a model, it’s a good idea to ask ourselves:
“Can this problem be solved without #ML?”
Yes? Then head on over to this article 👇
bit.ly/3fokz72
#MLOps stack at companies doing #ML at a reasonable scale.
How do they choose their tools?
Veeeeery pragmatically.
First thing is to understand what you actually need.
Which part of the stack you need to do well and which part not so much.
The secret key is the interoperability of the components.
That is the difference between success and frustration when building an #MLOps platform.
In the classic debate between build, in-house vs buy best-of-breed, the answer (when you cut the fluff out) is almost always both.