On Memory Construction and Retrieval for Personalized Conversational Agents https://arxiv.org/abs/2502.05589
491 karma · joined July 20, 2010
Founder, Lobe (acquired by Microsoft)
Love to chat - email is [username]@gmail.com
On Memory Construction and Retrieval for Personalized Conversational Agents https://arxiv.org/abs/2502.05589
Lobe will always let you train custom machine learning for free on your computer. We hope this becomes a vibrant ecosystem, and the business model around the edges can come later for value-add services.
* Easy to use - no coding, cloud configuration or machine learning experience required.
* Free & private - train for free on your own computer without uploading your data to the cloud. No accounts required.
* Ship anywhere - available for both Mac and Windows. Export your model and ship it on any platform you choose.
AutoML requires paid accounts with high friction setup and is focused on just training a model on your data. You would have to pay and retrain your model manually every time you want to make an iteration. Lobe gives fluidity with iterating and providing feedback to your model through Play.
The lobes in the UI are all essentially functions that you double click into to see the graph they use, all the way down to the theory/math.
If you want more comprehensive ways to learn the theory, I highly recommend Stanford's 231n course (http://cs231n.stanford.edu/) and the Goodfellow/Bengio/Courville Deep Learning book (https://www.amazon.com/Deep-Learning-Adaptive-Computation-Ma...)
Something really interesting we have discussed for a future feature is being able to train a model using the data of which architectures end up working best for different data types so that Lobe can use AutoML to suggest better templates starting out, or on the fly while you are building the model.
The architecture implemented using Lobes for object detection is called Yolo v2 (https://pjreddie.com/darknet/yolo/). It is fairly state-of-the-art for that type of problem and has ~70 million parameters that are being learned (matrices that get multiplied and added together). With a webcam and a GPU over the network, we typically see ~1-5 fps with a lot of network overhead sending output images - looking to make that faster for API deployment. The paper site above shows it having 62.94 Bn FLOPS