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

Using knitr chunks caching feature with Julia via JuliaCall knitr engine #38

Open
konstunn opened this issue Mar 30, 2018 · 2 comments
Open

Comments

@konstunn
Copy link

How can I use knitr caching feature with Julia via JuliaCall. Tell me, please, how can I achieve that, if it is possible?

And one more question is if it is possible to speed up loading Julia setup script? These two questions are relevant to each other in the aspect that I'm looking for speeding up my document build.

@konstunn
Copy link
Author

Oh, it seems that it is not that hard to make caching works. I got it work.

@Non-Contradiction
Copy link
Owner

The caching feature works except for the objects in julia, which of course can not be cached by R process.

I was once considering to cache julia objects if necessary by using some other julia packages, maybe looking for some julia functions like save.image in R and I can just use it?
And this feature will require to interact with knitr cache functionality, for example, knitr has some rules to make validation of the cached code chunk and etc.
There is some related and similar in nature discussion about cache of reticulate, which calls Python from R, at
yihui/knitr#1505
yihui/knitr#1518
and rstudio/reticulate#167
But I expect solving this problem in JuliaCall should be much easier.

It will be meaningful to have the feature which caches julia objects if needed. But I expect it to be a little complicated. And it doesn't have high priority currently. If you are interested in achieving this, we can discuss more about this, and a PR will be warmly welcomed.

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