Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lab Order - DuckDB used in Lab2 but created in Lab3 #251

Open
gmtanner-cord opened this issue May 7, 2024 · 1 comment
Open

Lab Order - DuckDB used in Lab2 but created in Lab3 #251

gmtanner-cord opened this issue May 7, 2024 · 1 comment

Comments

@gmtanner-cord
Copy link

I am reading through the book and working through the labs. I am considering using the early chapters of the book as a text for course that I am teaching in the fall.

I am running into some issues with Lab2 (model-vetiver.qmd). The file uses a duckdb for the palmerpenquins but the duckdb database isn't created until the next lab. I modified the file to be more similar to the first lab and that worked for that portion of the lab. [Still trying to get the pins storage to work].

@durraniu
Copy link

I've added 2 lines for adding penguins dataframe to duckdb in this issue.

What issue are you encountering with pins storage? In my case, this code cell works even if I do not create /data/model directory:

from pins import board_folder
from vetiver import vetiver_pin_write

model_board = board_folder("/data/model", allow_pickle_read = True)
vetiver_pin_write(model_board, v)

Running this code also does not create /data/model. And when I try to get the model back from pins, it works without any errors:
VetiverModel.from_pin(model_board, 'penguin_model')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants