ClojisR

Clojure speaks statistics - a jisr between Clojure and R

How to pronounce it?

The beginning of the pronunciation is the same as Clojure, but then it rhymes with 'kisser'. Actually, the last vowel is nonexistent, so you may try to pronounce it with less movement between s and r, like 'yesssr!'.

Status

• still evolving
• not recommended for production yet
• already used by several people in their data science explorations

Scope of the project

Libraries for Clojure-R interop are note new - see this list.

This project suggests yet another way to use R from Clojure.

Currently we target only JVM Clojure, but we are interested in generalizing the work to Clojurescript.

The related problem, of calling Clojure from R, may be addressed too in the future. We are experimenting with that.

Meta Goals

• Realize what is essential for Clojure to become a beginner-friendly solution for data science.

• Expose the Clojure ecosystem to a different culture and to more diverse groups of users/programmers.

Technical Goals

• A Function-centric API, where the default mode of usage is calling R functions on R objects, from Clojure (Status: supported)

• "R code as Clojure data", inspired by the EDN-based syntax inroducted in gg4clj and used in huri (Status: supported)

• Interop with minimal copying of data (Status: supported)

• Compatibility with common data abstractions such as tech.ml.dataset datasets (Status: partially supported)

• Convenient wrappers for common use cases, such as visualization (Status: basic support for plots and Rmarkdown)

• Abstraction over different runtimes (GNUR R, Renjin, FastR) (Status: GNU R is supported through Rserve; Renjin has some basic support)

• Convenient multi-session support (Status: basic support with some known issues)

Usage requirements

• Linux, MacOS or WSL (Windows Subsystem for Linux)

• JDK 1.8 or later

• Clojure 1.9.0 or later

• R

• The Rserve R package (install.packages("Rserve")) Tested with Rserve version 1.8.6. Earlier versions are known to have a bug. Rserve 1.8.6 is currently not on CRAN, but can be installed with install.packages("Rserve",,"http://rforge.net")

• This library

Setting up the logging

• clojisr library uses clojure/tools.logging for logging. tools.logging doesn't force any logging backend and users have to configure it on their side. To force specific backend you can set it using JVM options, for example in lein profile.clj or project.clj:

:jvm-opts ["-Dclojure.tools.logging.factory=clojure.tools.logging.impl/jul-factory"]

Checking if it works

This should work for you (assuming you have the clj tool):

$ clj -Sdeps '{:deps {scicloj/clojisr {:mvn/version "1.0.0-BETA8"}}}}'
Clojure 1.10.1
user=> (require '[clojisr.v1.r :refer [r]])

user=> (r '(+ 1 2))
[1] 3

Known issues

• clojisr can behave in a strange way when abandoned R (with Rserve) processes are running. Please kill such processes before creating an Rserve session.
• Nextjournal can hang due to problems with logging, please add org.slf4j/slf4j-nop {:mvn/version "1.7.30"} to the deps to disable logger.
• When an R dataframe contains columns of type "logical" (that is, boolean), these are not transferable to Clojure. We wait for an upcoming fix in tech.ml.dataset code.

Video presentations

The main ideas were discussed at Scicloj Web meeting #7 and ClojuTRE 2019.

Note however that:

• The API has changed since then (code generation mechanism, data visualization support, printing - see the Tutorials below).
• On the meeting, there is some careless use of the term 'zero copy'. Actually, what is usually meant by this term is not supported at the moment.

Tutorials

• Intro

• A tutorial about generating R code from Clojure

• Renjin backend

• Titanic tutorial #0

• More examples -- see the clojisr-examples repo

Background

1. Lisp for statistical computing

2. Calling R from Clojure: existing libraries

3. R backends

4. Some of R's data abstractions

5. Clojure's counterparts of R's data abstractions

Choices of the current project

Here are the current priorities of the project in some central design and implementation questions.

Future opportunities

Here are some possible future developments we are considering.

Discussion

Please share your comments, thoughts, ideas and questions at the Issues Page of this project and at the r-interop stream of the Clojurians Zulip.

Also we run a stream for developers or people interested in contributing.

Testing

The code tests are embedded in the tutorials and are run when they are rendered (using notespace). This way we make sure that tests and documentation are in sync.

Tools used

Working on this project, we enjoyed the following tools (partial list):

• In early versions, hara.test was used for automated docstrings by tests. We may come back to using it.

• clj-kondo for code quality control

• notespace for documentation and tests

License

Copyright © 2019 Scicloj

This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0 which is available at http://www.eclipse.org/legal/epl-2.0.

This Source Code may also be made available under the following Secondary Licenses when the conditions for such availability set forth in the Eclipse Public License, v. 2.0 are satisfied: GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version, with the GNU Classpath Exception which is available at https://www.gnu.org/software/classpath/license.html.