Closed rawkintrevo closed 1 week ago
We should group this recipe with the fine-tuning one in the ToC, but I can do that in a separate PR. (There's an existing story that I own covering this.)
Related to last comment: Let's adjust the intro language "We now demonstrate how to load a model back for inference." by adding a link to the previous recipe and reminding the reader of the context.
This recipe is testable. I happened to grant access to my HF_TOKEN during my run-through just now. Is that necessary? If so, we can get in available as an org-level secret.
I'm going to merge this as-is, but let's address the points in these 3 comments soon.
Agree on the cross links, my thought was get this one in, then link from the training notebook to this one, and this one back to the training one. The latter I could have done in this PR. (probably on the code one too).
On testable: I don't know if it is? In the test it will download and try to run the notebook. I don't know how that will work in a CPU only environment.
PR Checklist
Notebook requirements
Incoming References
GitHub