docs: production-deployment guide for trained FLAML models#1562
Open
immu4989 wants to merge 1 commit into
Open
docs: production-deployment guide for trained FLAML models#1562immu4989 wants to merge 1 commit into
immu4989 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
Adds a new
Use-Cases/Production-Deployment.mdpage covering the train → save → reload → predict on new data lifecycle, with a focus on the gotchas that actually surface in production but aren't in the quick-start tutorials.Each section is grounded in a real user-reported pain point — the page exists because the same handful of issues keep getting filed against FLAML at the inference boundary:
automl.model.estimators_[i].predict(raw_X)failsMultiOutputRegressor(AutoML())ignoresX_valsample_weight+split_type="time"AttributeErrorThe page follows the existing
Use-Cases/style (it sits next toTask-Oriented-AutoML.md,Zero-Shot-AutoML.md, andTune-User-Defined-Function.md) and is picked up automatically by the sidebar ({type: 'autogenerated', dirName: 'Use-Cases'}inwebsite/sidebars.js).Pre-flight verification
Every runnable snippet on the page was exercised against current
mainbefore writing. One discovery from that pre-flight is worth flagging in review: the MLflow autolog example inBest-Practices.md, as written, reloads as an unfittedPipelineon recent MLflow versions (verified onmlflow==2.22.1). The new page recommends the explicitmlflow.sklearn.log_model(automl, artifact_path="...")pattern instead, which round-trips correctly. Happy to file a follow-up bug for the autolog reload path if useful.What the page does not cover
Task-Oriented-AutoML.md).Zero-Shot-AutoML.md).Related issue / PR list
This page references but does not duplicate:
Checks