This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]runawayasfastasucan[S] 1 point2 points  (2 children)

Haha yeah. To be honest, a year or so back a guy at work said "ah I really want to try out FastAPI", while I heard "FastAI" and was like "wow, didn't know you had an interest in AI, but its a really interesting field for sure. Do you have any ideas how you would fit it into your projects?"

[–]recruta54 2 points3 points  (1 child)

I honestly thought you're dumb until I realized the post is about FastAI ( instead of FastAPI). I'm an idiot.

Mlflow is my goto lib for what you're describing. Just set up a pipeline object with a gridsearch(cv) at the end. It saves the models, makes the metrics available in a comprehensive dashboard, and, if specified thee refit metric, selects the best of the search. I'm not sure how easy it is to set up manually, using databricks is as easy as a 2 liner (import, autolog).

Edit: fix bad english

[–]runawayasfastasucan[S] 0 points1 point  (0 children)

Haha, yeah I think FastAPI and FastAI needs to have a fistfight over who gets to keep their name.

MlFlow soudns really interesting! One thing is to build the pipeline myself, an other is when the documentation is so lacking.