You can store and version your model by choosing a pins “board” for it. Your board for model pins can be set up to use a local folder, Posit Connect, Amazon S3, and more. When we write the vetiver model to our board, the binary model object is stored on our board together with necessary metadata, like the packages needed to make a prediction and the model’s input data prototype for checking new data at prediction time.
Note
We’ll use a temporary board that will be automatically deleted for this demo, but for your real work, you will want to choose the best board for your particular infrastructure.
# A tibble: 2 × 3
version created hash
<chr> <dttm> <chr>
1 20230525T215011Z-b7182 2023-05-25 21:50:11 b7182
2 20230525T215013Z-30bc2 2023-05-25 21:50:13 30bc2
model_board.pin_versions("cars_mpg")
created hash version
0 2023-05-25 21:50:11 dc1c1 20230525T215011Z-dc1c1
1 2023-05-25 21:50:13 a9338 20230525T215013Z-a9338
The primary purpose of pins is to make it easy to share data artifacts, so depending on the board you choose, your pinned vetiver model can be shareable with your collaborators.