The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
julia chunk (#209).julia_setup now allows for passing version
to override the default automatically downloaded version from
"latest"julia_command and julia_eval. Fix #161.R_user_dir to get default julia installation
position on R 4.0.sysimage_path
argument to the function julia_setup allows either an
absolute path to the image, or a path relative to the current directory.
(#155 by @JackDunnNZ).ERROR: could not load library on
Debian/Ubuntu and other systems which build Julia with
MULTIARCH_INSTALL=1 (#143 by @liskin).install_julia function for automatic installation
of julia. (#135 by @christopher-dG).julia_setup() for custom sysimage loading (#140 by @dgrominski).julia_setup() for
automatic installation of Julia when Julia is not found.julia_markdown_setup for setup of JuliaCall in
RMarkdown document and notebook explicitly. Related to #98 and
#132.autowrap.julia_function, julia_pkg_import, and
julia_pkg_hook.$.() for Julia callable object
syntax.julia_install_package accepts URLs to install packages,
fix #106.julia_setup, fix #105.rebuild argument in the function
julia_setup. The argument controls whether to rebuild
RCall.jl, whose default value is FALSE to save
startup time. If a new version of R is used, then this parameter needs
to be set to TRUE.JuliaObject, which frees the
JuliaObject on the Julia side after it’s freed
on the R side.engine.path option for Julia in
RMarkdown document.Julia knitr engine to avoid use
of knitr internal functions.Julia stdout in RMarkdown documents.Julia v0.7/1.0.Julia v0.7.JuliaCall is now compatible with RCall.jl
v0.11.0 on Julia v0.7.Pkg.build("RCall").Julia v1.0.Julia v0.7 and
v1.0.JuliaCall now should be usable on Julia
v0.7 and Julia v1.0 with released version of
RCall.julia_source on Julia
v0.7 and v1.0.julia_check which is deprecated a long time
ago.install argument in julia_setup(),
setting it to FALSE can reduce startup time when no
installation or checking of dependent Julia packages is
needed.julia_console().R6 dependency to reduce overhead creating
JuliaObject.Julia v0.7, currently need to use
RCall#e59a546 with JuliaCall on
Julia v0.7.Julia v0.7.diff.JuliaObject.JuliaObject to that
in native R.is.numeric for
JuliaObject.c.JuliaObject.install_dependency not muted.julia_call
interface functions.sexp, rcopy
and creation of JuliaObject.julia$simple_call interface which is a simple
and more performant “equivalent” of the julia_call
interface.JuliaCall from
Rcpp.as.vector.JuliaObject.as.double.JuliaObject.JuliaObject supports multiple index.mean, determinant and
solve generics for JuliaObject.c and t generics for
JuliaObject.aperm, dim<- and
as.vector generics for JuliaObject.julia_setup(verbose = TRUE).need_return argument to julia_eval,
now there is a possibility to return the result as an
JuliaObject, which is convenient for many use cases
requiring an R object corresponding to a julia object.JuliaObject.rep.JuliaObject.JuliaObject.assign! to match behavior for assign
in R and use it for JuliaObject.JuliaPlain idea to alleviate the problem
that R dispatches only on the first argument, make ifelse
possible to work for JuliaObject.JuliaCall from julia
and RCall.jl.dim.JuliaObject,
is.array.JuliaObject and
is.matrix.JuliaObject.autowrap, which can generates automatic wrappers
for julia types.julia_docall and
julia_call.JuliaObject, especially in
Rmd documents. Fix #43.x$name could be used to get access to
field(x, name) for JuliaObject.RCall checking.julia issue #14577.JULIA_HOME.julia_setup()julia engine in Rnw
files.JuliaCall in rtichoke.JuliaCall requires Julia 0.6 as Julia 0.5 is now
officially unmaintained.julia_setup()
any more, accelerate the startup time.julia_setup.julia_setup() fails to correctly load
libjulia.dll if JULIA_HOME is not in path on windows.julia_eval_string.JuliaCall RMarkdown engine. The display system
should work for all kinds of documents that RMarkdown supports.JuliaObject, for more detail, see
github issue #15, issue #12 and #13 are related.JuliaObject, and fix many small
bugs.fields, field and
field<- function for JuliaObjects.JuliaObject. It’s
lightweight, faster, and safer.plotsViewer(), which
integrates better into R.JuliaCall, like removing
deprecated functions.JuliaObject, same Julia object could enter
julia_object_dict only once. And the display of JuliaObject
becomes better. Also every common types of Julia Object could be wrapped
by JuliaObject.JuliaObject type
return value instead of R Object.julia_call interface.julia_eval_string is deprecated in favor of
julia_eval.JuliaObject, which serves as a proxy in R for julia
object, which is the automatic conversion target when other choices are
not possible.julia_setup() doesn’t need to be called first unless
you want to force julia to restart or you need to set the julia
path.julia.do_call and julia_call now accept
keyword arguments.JuliaCall works in Jupyter R notebook.JuliaCall works in R Markdown. The display system
currently only work for html document. When there is no
return from julia function and there is a need to display, a div with
class=‘JuliaDisplay’ will be inserted into the html document with the
corresponding content.JuliaCall.JuliaCall is more consistent with julia.NEWS.md file to track changes to the
package.julia_assign which can assign a value to a name in
julia with automatic type conversion.julia_check.julia_console. Now there is a fully functional julia
repl in R terminal, and a usable julia console when you use IDE for
R.julia_setup, there is an option whether or not to
use RCall.jl, RCall’s R REPL mode and rgui will be set correctly.julia_setup for initial setup of
JuliaCall.julia_eval_string, julia_command for
executing commands in julia.julia_do.call and julia_call for calling
functions in julia.julia_help.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.