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

Pins as a possible future target data object #1045

Closed
asadow opened this issue Apr 11, 2023 · 3 comments
Closed

Pins as a possible future target data object #1045

asadow opened this issue Apr 11, 2023 · 3 comments
Assignees

Comments

@asadow
Copy link

asadow commented Apr 11, 2023

Is there any plan to allow pins as target data objects? My use case would be version control inside OneDrive, with pins potentially living outside the project folder.

@wlandau
Copy link
Collaborator

wlandau commented Apr 12, 2023

You can invoke pins in a target if you call pins::board_register_github() and then pins::pin() inside the command of a target. The idea is very similar to my sketch of a vetiver pipeline at #1001. I do not plan to create a special storage format for a pin because pins are usually downstream of everything else and do not typically have other targets that depend on them.

@wlandau wlandau closed this as completed Apr 12, 2023
@wlandau
Copy link
Collaborator

wlandau commented Jun 22, 2023

That said, you can define your own pin format with targets::tar_format().

@wlandau
Copy link
Collaborator

wlandau commented Jun 22, 2023

In fact, I plan to recommend tar_format() going forward for these specialized cases. (I wish I had done this from the beginning for format = "keras" and format = "torch").

I am still open to consider new formats if they apply to more general kinds of R objects: for example, for data frames, if something ever supersedes or outperforms arrow.

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

No branches or pull requests

2 participants