galaaz 0.4.1 → 0.4.2

data/blogs/gknit/gknit.tex

@@ -0,0 +1,745 @@
+\documentclass[]{article}
+\usepackage{lmodern}
+\usepackage{amssymb,amsmath}
+\usepackage{ifxetex,ifluatex}
+\usepackage{fixltx2e} % provides \textsubscript
+\ifnum 0\ifxetex 1\fi\ifluatex 1\fi=0 % if pdftex
+  \usepackage[T1]{fontenc}
+  \usepackage[utf8]{inputenc}
+\else % if luatex or xelatex
+  \ifxetex
+    \usepackage{mathspec}
+  \else
+    \usepackage{fontspec}
+  \fi
+  \defaultfontfeatures{Ligatures=TeX,Scale=MatchLowercase}
+\fi
+% use upquote if available, for straight quotes in verbatim environments
+\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
+% use microtype if available
+\IfFileExists{microtype.sty}{%
+\usepackage{microtype}
+\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
+}{}
+\usepackage[margin=1in]{geometry}
+\usepackage{hyperref}
+\hypersetup{unicode=true,
+            pdftitle={gKnit - Ruby and R Knitting with Galaaz in GraalVM},
+            pdfauthor={Rodrigo Botafogo},
+            pdfborder={0 0 0},
+            breaklinks=true}
+\urlstyle{same}  % don't use monospace font for urls
+\usepackage{color}
+\usepackage{fancyvrb}
+\newcommand{\VerbBar}{|}
+\newcommand{\VERB}{\Verb[commandchars=\\\{\}]}
+\DefineVerbatimEnvironment{Highlighting}{Verbatim}{commandchars=\\\{\}}
+% Add ',fontsize=\small' for more characters per line
+\usepackage{framed}
+\definecolor{shadecolor}{RGB}{248,248,248}
+\newenvironment{Shaded}{\begin{snugshade}}{\end{snugshade}}
+\newcommand{\KeywordTok}[1]{\textcolor[rgb]{0.13,0.29,0.53}{\textbf{#1}}}
+\newcommand{\DataTypeTok}[1]{\textcolor[rgb]{0.13,0.29,0.53}{#1}}
+\newcommand{\DecValTok}[1]{\textcolor[rgb]{0.00,0.00,0.81}{#1}}
+\newcommand{\BaseNTok}[1]{\textcolor[rgb]{0.00,0.00,0.81}{#1}}
+\newcommand{\FloatTok}[1]{\textcolor[rgb]{0.00,0.00,0.81}{#1}}
+\newcommand{\ConstantTok}[1]{\textcolor[rgb]{0.00,0.00,0.00}{#1}}
+\newcommand{\CharTok}[1]{\textcolor[rgb]{0.31,0.60,0.02}{#1}}
+\newcommand{\SpecialCharTok}[1]{\textcolor[rgb]{0.00,0.00,0.00}{#1}}
+\newcommand{\StringTok}[1]{\textcolor[rgb]{0.31,0.60,0.02}{#1}}
+\newcommand{\VerbatimStringTok}[1]{\textcolor[rgb]{0.31,0.60,0.02}{#1}}
+\newcommand{\SpecialStringTok}[1]{\textcolor[rgb]{0.31,0.60,0.02}{#1}}
+\newcommand{\ImportTok}[1]{#1}
+\newcommand{\CommentTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textit{#1}}}
+\newcommand{\DocumentationTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textbf{\textit{#1}}}}
+\newcommand{\AnnotationTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textbf{\textit{#1}}}}
+\newcommand{\CommentVarTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textbf{\textit{#1}}}}
+\newcommand{\OtherTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{#1}}
+\newcommand{\FunctionTok}[1]{\textcolor[rgb]{0.00,0.00,0.00}{#1}}
+\newcommand{\VariableTok}[1]{\textcolor[rgb]{0.00,0.00,0.00}{#1}}
+\newcommand{\ControlFlowTok}[1]{\textcolor[rgb]{0.13,0.29,0.53}{\textbf{#1}}}
+\newcommand{\OperatorTok}[1]{\textcolor[rgb]{0.81,0.36,0.00}{\textbf{#1}}}
+\newcommand{\BuiltInTok}[1]{#1}
+\newcommand{\ExtensionTok}[1]{#1}
+\newcommand{\PreprocessorTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textit{#1}}}
+\newcommand{\AttributeTok}[1]{\textcolor[rgb]{0.77,0.63,0.00}{#1}}
+\newcommand{\RegionMarkerTok}[1]{#1}
+\newcommand{\InformationTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textbf{\textit{#1}}}}
+\newcommand{\WarningTok}[1]{\textcolor[rgb]{0.56,0.35,0.01}{\textbf{\textit{#1}}}}
+\newcommand{\AlertTok}[1]{\textcolor[rgb]{0.94,0.16,0.16}{#1}}
+\newcommand{\ErrorTok}[1]{\textcolor[rgb]{0.64,0.00,0.00}{\textbf{#1}}}
+\newcommand{\NormalTok}[1]{#1}
+\usepackage{graphicx,grffile}
+\makeatletter
+\def\maxwidth{\ifdim\Gin@nat@width>\linewidth\linewidth\else\Gin@nat@width\fi}
+\def\maxheight{\ifdim\Gin@nat@height>\textheight\textheight\else\Gin@nat@height\fi}
+\makeatother
+% Scale images if necessary, so that they will not overflow the page
+% margins by default, and it is still possible to overwrite the defaults
+% using explicit options in \includegraphics[width, height, ...]{}
+\setkeys{Gin}{width=\maxwidth,height=\maxheight,keepaspectratio}
+\IfFileExists{parskip.sty}{%
+\usepackage{parskip}
+}{% else
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{6pt plus 2pt minus 1pt}
+}
+\setlength{\emergencystretch}{3em}  % prevent overfull lines
+\providecommand{\tightlist}{%
+  \setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
+\setcounter{secnumdepth}{5}
+% Redefines (sub)paragraphs to behave more like sections
+\ifx\paragraph\undefined\else
+\let\oldparagraph\paragraph
+\renewcommand{\paragraph}[1]{\oldparagraph{#1}\mbox{}}
+\fi
+\ifx\subparagraph\undefined\else
+\let\oldsubparagraph\subparagraph
+\renewcommand{\subparagraph}[1]{\oldsubparagraph{#1}\mbox{}}
+\fi
+
+%%% Use protect on footnotes to avoid problems with footnotes in titles
+\let\rmarkdownfootnote\footnote%
+\def\footnote{\protect\rmarkdownfootnote}
+
+%%% Change title format to be more compact
+\usepackage{titling}
+
+% Create subtitle command for use in maketitle
+\newcommand{\subtitle}[1]{
+  \posttitle{
+    \begin{center}\large#1\end{center}
+    }
+}
+
+\setlength{\droptitle}{-2em}
+
+  \title{gKnit - Ruby and R Knitting with Galaaz in GraalVM}
+    \pretitle{\vspace{\droptitle}\centering\huge}
+  \posttitle{\par}
+    \author{Rodrigo Botafogo}
+    \preauthor{\centering\large\emph}
+  \postauthor{\par}
+      \predate{\centering\large\emph}
+  \postdate{\par}
+    \date{19 October 2018}
+
+% usar portugues do Brasil
+% \usepackage[brazilian]{babel}
+\usepackage[utf8]{inputenc}
+
+\usepackage{geometry}
+\geometry{a4paper, top=1in}
+
+% necessários para uso com kableExtra
+\usepackage{longtable}
+\usepackage{multirow}
+\usepackage[table]{xcolor}
+\usepackage{wrapfig}
+\usepackage{float}
+\usepackage{colortbl}
+\usepackage{pdflscape}
+\usepackage{tabu}
+\usepackage{threeparttable}
+\usepackage[normalem]{ulem}
+
+\usepackage{bbm}
+\usepackage{booktabs}
+\usepackage{expex}
+
+\usepackage{graphicx}
+\usepackage{fancyhdr}
+\pagestyle{fancy}
+\fancyhf{}
+
+\usepackage{lipsum}
+
+% disponibilizar o comando lastpage
+\usepackage{lastpage}
+
+% tamanho do font padrão 11pt
+\usepackage[fontsize=10pt]{scrextend}
+
+% comandos para formatar uma tabela
+\usepackage{array}
+\newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+\newcolumntype{C}[1]{>{\centering\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+\newcolumntype{R}[1]{>{\raggedleft\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
+
+% necessário para importar outros arquivos latex
+\usepackage{import}
+
+\newcommand{\RtoLatex}[2]{\newcommand{#1}{#2}}
+%\newcommand{\atraso}[1]{\color{red} \textbf {Tempo desde a Assinatura do Contrato: #1 dias}}
+
+\begin{document}
+\maketitle
+
+\section{Introduction}\label{introduction}
+
+The idea of ``literate programming'' was first introduced by Donald
+Knuth in the 1980's. The main intention of this approach was to develop
+software interspersing macro snippets, traditional source code, and a
+natural language such as English that could be compiled into executable
+code and at the same time easily read by a human developer. According to
+Knuth ``The practitioner of literate programming can be regarded as an
+essayist, whose main concern is with exposition and excellence of
+style.''
+
+The idea of literate programming envolved into the idea of reproducible
+research, in which all the data, software code, documentation, graphics
+etc. needed to reproduce the research and its reports could be included
+in a single document or set of documents that when distributed to peers
+could be rerun generating the same output and reports.
+
+The R community has put a great deal of effort in reproducible research.
+In 2002, Sweave was introduced and it allowed mixing R code with Latex
+generating hight quality PDF documents. Those documents could include
+the code, the result of executing the code, graphics and text. This
+contained the whole narrative to reproduce the research. But Sweave had
+many problems and in 2012, Knitr, developed by Yihui Xie from RStudio
+was released, solving many of the long lasting problems from Sweave and
+including in one single package many extensions and add-on packages that
+were necessary for Sweave.
+
+With Knitr, R markdown was also developed, an extension the the Markdown
+format. With R markdown and Knitr it is possible to generate reports in
+a multitude of formats such as HTML, markdown, Latex, PDF, dvi, etc. R
+markdown also allows the use of multiple programming languages in the
+same document. In R markdown text is interspersed with code chunks that
+can be executed and both the code as the result of executing the code
+can become part of the final report. Although R markdown allows multiple
+programming languages in the same document, only R and Python (with the
+reticulate package) can persist variables between chunks. For other
+languages, such as Ruby, every chunk will start a new process and thus
+all data is lost between chunks, unless it is somehow stored in a data
+file that is read by the next chunk.
+
+Being able to persist data between chunks is critical for literate
+programming otherwise the flow of the narrative is lost by all the
+effort of having to save data and then reload it. Probably, because of
+this impossibility, it is very rare to see any R markdown document
+document in the Ruby community.
+
+In the Python community, the same effort to have code and text in an
+integrated environment started also on the first decade of 2000. In 2006
+iPython 0.7.2 was released. In 2014, Fernando Pérez, spun off project
+Jupyter from iPython creating a web-based interactive computation
+environment. Jupyter can now be used with many languages, including Ruby
+with the iruby gem (\url{https://github.com/SciRuby/iruby}). I am not
+sure if multiple languages can be used in a Jupyter notebook.
+
+\section{gKnitting a Document}\label{gknitting-a-document}
+
+This document describes gKnit. gKnit uses Knitr and R markdown to knit a
+document in Ruby or R and output it in any of the available formats for
+R markdown. The only difference between gKnit and normal Knitr documents
+is that gKnit runs atop of GraalVM, and Galaaz (an integration library
+between Ruby and R). Another blog post on Galaaz and its integration
+with ggplot2 can be found at:
+\url{https://towardsdatascience.com/ruby-plotting-with-galaaz-an-example-of-tightly-coupling-ruby-and-r-in-graalvm-520b69e21021}.
+With Galaaz, gKnit can knit documents in Ruby and R and both Ruby and R
+execute on the same process and memory, variables, classes, etc. will be
+preserved between chunks of code.
+
+This is not a blog post on rmarkdown, and the interested user is
+directed to
+
+\begin{itemize}
+\tightlist
+\item
+  \url{https://rmarkdown.rstudio.com/} or
+\item
+  \url{https://bookdown.org/yihui/rmarkdown/} for detailed information
+  on its capabilities and use.
+\end{itemize}
+
+Here, we will describe quickly the main aspects of R markdown, so the
+user can start gKnitting Ruby and R documents quickly.
+
+\subsection{The Yaml header}\label{the-yaml-header}
+
+An R markdown document should start with a Yaml header and be stored in
+a file with `.Rmd' extension. This document has the following header for
+gKitting an HTML document.
+
+\begin{verbatim}
+---
+title: "gKnit - Ruby and R Knitting with Galaaz in GraalVM"
+author: "Rodrigo Botafogo"
+tags: [Galaaz, Ruby, R, TruffleRuby, FastR, GraalVM, knitr, gknit]
+date: "29 October 2018"
+output:
+  html_document:
+    keep_md: true
+---
+\end{verbatim}
+
+For more information on the options in the Yaml header, check
+\url{https://bookdown.org/yihui/rmarkdown/html-document.html}.
+
+\subsection{R Markdown formatting}\label{r-markdown-formatting}
+
+Document formating can be done with simple markups such as:
+
+\subsubsection{Headers}\label{headers}
+
+\begin{verbatim}
+# Header 1
+
+## Header 2
+
+### Header 3
+\end{verbatim}
+
+\subsubsection{Lists}\label{lists}
+
+\begin{verbatim}
+Unordered lists:
+
+* Item 1
+* Item 2
+    + Item 2a
+    + Item 2b
+\end{verbatim}
+
+\begin{verbatim}
+Ordered Lists
+
+1. Item 1
+2. Item 2
+3. Item 3
+    + Item 3a
+    + Item 3b
+\end{verbatim}
+
+Please, go to \url{https://rmarkdown.rstudio.com/authoring_basics.html},
+for more R markdown formating.
+
+\subsection{Code Chunks}\label{code-chunks}
+
+Running and executing Ruby and R code is actually what really interests
+us is this blog. Inserting a code chunk is done by adding code in a
+block delimited by three back ticks followed by a block with the engine
+name (r, ruby, rb, include, others), an optional chunk\_label and
+optional options, as shown bellow:
+
+\begin{verbatim}
+```{engine_name [chunk_label], [chunk_options]}
+```
+\end{verbatim}
+
+for instance, let's add an R chunk to the document labeled
+`first\_r\_chunk'. In this case, the code should not be shown in the
+document, so the option `echo=FALSE' was added.
+
+\begin{verbatim}
+```{r first_r_chunk, echo = FALSE}
+```
+\end{verbatim}
+
+A description of the available chunk options can be found in the
+documentation cited above.
+
+For including a Ruby chunk, just change the name of the engine to ruby
+as follows:
+
+\begin{verbatim}
+```{ruby first_ruby_chunk}
+```
+\end{verbatim}
+
+In this example, the ruby chunk is called `first\_ruby\_chunk'. One
+important aspect of chunk labels is that they cannot be duplicate. If a
+chunk label is duplicate, the knitting will stop with an error.
+
+\subsubsection{R chunks}\label{r-chunks}
+
+Let's now add an R chunk to this document. In this example, a vector
+`r\_vec' is created and a new function `redundat\_sum' is defined. The
+chunk specification is
+
+\begin{verbatim}
+```{r data_creation}
+r_vec <- c(1, 2, 3, 4, 5)
+
+redef_sum <- function(...) {
+  Reduce(sum, as.list(...))
+}
+```
+\end{verbatim}
+
+and this is how it will look like once executed. From now on, we will
+not show the chunk definition any longer.
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\NormalTok{r_vec <-}\StringTok{ }\KeywordTok{c}\NormalTok{(}\DecValTok{1}\NormalTok{, }\DecValTok{2}\NormalTok{, }\DecValTok{3}\NormalTok{, }\DecValTok{4}\NormalTok{, }\DecValTok{5}\NormalTok{)}
+
+\NormalTok{redef_sum <-}\StringTok{ }\ControlFlowTok{function}\NormalTok{(...) \{}
+  \KeywordTok{Reduce}\NormalTok{(sum, }\KeywordTok{as.list}\NormalTok{(...))}
+\NormalTok{\}}
+\end{Highlighting}
+\end{Shaded}
+
+We can, possibly in another chunk, access the vector and call the
+function as follows:
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\KeywordTok{print}\NormalTok{(r_vec)}
+\end{Highlighting}
+\end{Shaded}
+
+\begin{verbatim}
+## [1] 1 2 3 4 5
+\end{verbatim}
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\KeywordTok{print}\NormalTok{(}\KeywordTok{redef_sum}\NormalTok{(r_vec))}
+\end{Highlighting}
+\end{Shaded}
+
+\begin{verbatim}
+## [1] 15
+\end{verbatim}
+
+\subsubsection{Ruby chunks}\label{ruby-chunks}
+
+In the same way that an R chunk was created, let's now create a Ruby
+chunk. One important aspect of Ruby is that in Ruby every evaluation of
+a chunk occurs on its own local scope, so, creating a variable in a
+chunk will be out of scope in the next chunk. To make sure that
+variables are available between chunks, they should be made global.
+
+In this chunk, variable `\$a', `\$b' and `\$c' are standard Ruby
+variables and `\$vec' and `\$vec2' are two vectors created by a call to
+FastR. It should be clear that there is no requirement in gknit to call
+or use R functions. gKnit will knit standard Ruby code, or even general
+text without code.
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\DataTypeTok{$a}\NormalTok{ = [}\DecValTok{1}\NormalTok{, }\DecValTok{2}\NormalTok{, }\DecValTok{3}\NormalTok{]}
+\DataTypeTok{$b}\NormalTok{ = }\StringTok{"US$ 250.000"}
+\DataTypeTok{$c}\NormalTok{ = }\StringTok{"Inline text in a Heading"}
+
+\DataTypeTok{$vec}\NormalTok{ = R.c(}\DecValTok{1}\NormalTok{, }\DecValTok{2}\NormalTok{, }\DecValTok{3}\NormalTok{)}
+\DataTypeTok{$vec2}\NormalTok{ = R.c(}\DecValTok{10}\NormalTok{, }\DecValTok{20}\NormalTok{, }\DecValTok{30}\NormalTok{)}
+\end{Highlighting}
+\end{Shaded}
+
+In this next block, variables `\$a', `\$vec' and `\$vec2' are used and
+printed.
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\NormalTok{puts }\DataTypeTok{$a}
+\NormalTok{puts }\DataTypeTok{$vec}\NormalTok{ * }\DataTypeTok{$vec2}
+\end{Highlighting}
+\end{Shaded}
+
+\begin{verbatim}
+## 1
+## 2
+## 3
+## [1] 10 40 90
+\end{verbatim}
+
+\subsubsection{Accessing R from Ruby}\label{accessing-r-from-ruby}
+
+One of the nice aspects of Galaaz on GraalVM, is that variables and
+functions defined in R, can be easily accessed from Ruby. This next
+chunk, reads data from R and uses the `redef\_fun' function defined
+previously. To access an R variable from Ruby the `\textasciitilde{}'
+function shoud be applied to the Ruby symbol representing the R
+variable. Since the R variable is called `r\_vec', in Ruby, the symbol
+to acess it is `:r\_vec' and thus `\textasciitilde{}:r\_vec' retrieves
+the value of the variable.
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\NormalTok{puts ~}\StringTok{:r_vec}
+\end{Highlighting}
+\end{Shaded}
+
+\begin{verbatim}
+## [1] 1 2 3 4 5
+\end{verbatim}
+
+In order to call an R function, the `R.' module is used as follows
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\NormalTok{puts R.redef_sum(}\DataTypeTok{$vec}\NormalTok{)}
+\end{Highlighting}
+\end{Shaded}
+
+\begin{verbatim}
+## [1] 6
+\end{verbatim}
+
+\subsubsection{Inline Ruby code}\label{inline-ruby-code}
+
+Knitr allows inserting R inline by adding `r code` . Unfortunately, this
+is not possible with Ruby code as there is no provision in knitr for
+adding this kind of inline engine. However, gKnit allows adding inline
+Ruby code with the `rb' engine. The following text will create and
+inline Ruby text:
+
+\begin{verbatim}
+This is some text with inline Ruby accessing variable \$b which has value:
+```{rb puts $b}
+```
+and is followed by some other text!
+\end{verbatim}
+
+The result of executing the above ckunk is the following sentence with
+inline Ruby code
+
+This is some text with inline Ruby accessing variable \$b which has
+value: US\$ 250.000 and is followed by some other text!
+
+In an inline block, it is possible to execute multiple Ruby statements
+by adding a semicolom between them:
+
+\begin{verbatim}
+Multiple statements in the 'rb' engine use semicolom:
+```{rb puts $a, puts $b}
+```
+\end{verbatim}
+
+Multiple statements in the `rb' engine use semicolom: 1 2 3 US\$ 250.000
+
+\subsubsection{Inline text in a Heading}\label{inline-text-in-a-heading}
+
+Sometimes one wants to add an inline text in a heading. To do that in
+Ruby the whole heading needs to be returned by the inline Ruby engine.
+For example the heading above, was created by the following chunk:
+
+\begin{verbatim}
+```{rb puts "### #{$c}"}
+```
+\end{verbatim}
+
+Remember that variable `\$\c' was defined in a previous Ruby chunk and
+is now being used to create the section heading for this section.
+
+\subsubsection{Including Ruby files}\label{including-ruby-files}
+
+R is a language that was created to be easy and fast for statisticians
+to use. It was not a language to be used for developing large systems.
+Of course, there are large systems and libraries in R, but the focus of
+the language is for developing statistical models and distribute that to
+peers.
+
+Ruby on the other hand, is a language for large software development.
+Systems written in Ruby will have dozens or hundreds of files. In order
+to document a large system with literate programming we cannot expect
+the developer to add all the files in a single `.Rmd' file. gKnit
+provides the `include' chunk engine to include a Ruby file as if it had
+being typed in the `.Rmd' file.
+
+To include a file the following chunk should be created, whre is the
+name of the file to be include and where the extension, if it is `.rb',
+does not need to be added. If the `relative' option is not included,
+then it is treated as TRUE. When `relative' is true, `require\_relative'
+semantics is used to load the file, when false, Ruby's \$LOAD\_PATH is
+searched to find the file and it is 'require'd.
+
+\begin{verbatim}
+```{include <filename>, relative = <TRUE/FALSE>}
+```
+\end{verbatim}
+
+Here we include file `model.rb' which is in the same directory of this
+blog. This code uses R `caret' package to split a dataset in a train and
+test sets.
+
+\begin{verbatim}
+```{include model}
+```
+\end{verbatim}
+
+\begin{verbatim}
+require 'galaaz'
+
+# Loads the R 'caret' package.  If not present, installs it 
+R.install_and_loads 'caret'
+
+class Model
+  
+  attr_reader :data
+  attr_reader :test
+  attr_reader :train
+
+  #==========================================================
+  #
+  #==========================================================
+  
+  def initialize(data, percent_train:, seed: 123)
+
+    R.set__seed(seed)
+    @data = data
+    @percent_train = percent_train
+    @seed = seed
+    
+  end
+
+  #==========================================================
+  #
+  #==========================================================
+
+  def partition(field)
+
+    train_index =
+      R.createDataPartition(@data.send(field), p: @percet_train,
+                            list: false, times: 1)
+    @train = @data[train_index, :all]
+    @test = @data[-train_index, :all]
+    
+  end
+  
+end
+\end{verbatim}
+
+\begin{Shaded}
+\begin{Highlighting}[]
+\NormalTok{mtcars = ~}\StringTok{:mtcars}
+\NormalTok{model = }\DataTypeTok{Model}\NormalTok{.new(mtcars, }\StringTok{percent_train: }\FloatTok{0.8}\NormalTok{)}
+\NormalTok{model.partition(}\StringTok{:mpg}\NormalTok{)}
+\NormalTok{puts model.train.head}
+\NormalTok{puts model.test.head}
+\end{Highlighting}
+\end{Shaded}
+
+\begin{verbatim}
+##                    mpg cyl  disp  hp drat    wt  qsec vs am gear carb
+## Datsun 710        22.8   4 108.0  93 3.85 2.320 18.61  1  1    4    1
+## Hornet 4 Drive    21.4   6 258.0 110 3.08 3.215 19.44  1  0    3    1
+## Hornet Sportabout 18.7   8 360.0 175 3.15 3.440 17.02  0  0    3    2
+## Merc 240D         24.4   4 146.7  62 3.69 3.190 20.00  1  0    4    2
+## Merc 280          19.2   6 167.6 123 3.92 3.440 18.30  1  0    4    4
+## Merc 280C         17.8   6 167.6 123 3.92 3.440 18.90  1  0    4    4
+##                mpg cyl  disp  hp drat    wt  qsec vs am gear carb
+## Mazda RX4     21.0   6 160.0 110 3.90 2.620 16.46  0  1    4    4
+## Mazda RX4 Wag 21.0   6 160.0 110 3.90 2.875 17.02  0  1    4    4
+## Valiant       18.1   6 225.0 105 2.76 3.460 20.22  1  0    3    1
+## Duster 360    14.3   8 360.0 245 3.21 3.570 15.84  0  0    3    4
+## Merc 230      22.8   4 140.8  95 3.92 3.150 22.90  1  0    4    2
+## Merc 450SE    16.4   8 275.8 180 3.07 4.070 17.40  0  0    3    3
+\end{verbatim}
+
+\subsubsection{Documenting Gems}\label{documenting-gems}
+
+\begin{verbatim}
+# Copyright (c) 2017 Oracle and/or its affiliates. All rights reserved. This
+# code is released under a tri EPL/GPL/LGPL license. You can use it,
+# redistribute it and/or modify it under the terms of the:
+#
+# Eclipse Public License version 1.0, or
+# GNU General Public License version 2, or
+# GNU Lesser General Public License version 2.1.
+
+warn "#{File.basename(__FILE__)}: warning: callcc is obsolete; use Fiber instead"
+
+class Continuation
+  def initialize
+    @fiber = Fiber.current
+  end
+
+  def call
+    if Fiber.current != @fiber
+      raise 'continuation called across fiber'
+    end
+    raise 'Continuations are unsupported on TruffleRuby'
+  end
+end
+
+module Kernel
+  def callcc
+    yield Continuation.new
+  end
+  module_function :callcc
+end
+\end{verbatim}
+
+\subsection{Converting to PDF}\label{converting-to-pdf}
+
+One of the beauties of knitr is that the same input can be converted to
+many different outputs. One very useful format, is, of course, PDF. In
+order to converted an R markdown file to PDF it is necessary to have
+LaTeX installed on the system. We will not explain here how to install
+LaTeX as there are plenty of documents on the web showing how to
+proceed.
+
+gKnit comes with a simple LaTeX style file for gknitting this blog as a
+PDF document. Here is the Yaml header to generate this blog in PDF
+format instead of HTML:
+
+\begin{verbatim}
+---
+title: "gKnit - Ruby and R Knitting with Galaaz in GraalVM"
+author: "Rodrigo Botafogo"
+tags: [Galaaz, Ruby, R, TruffleRuby, FastR, GraalVM, knitr, gknit]
+date: "29 October 2018"
+output:
+  pdf_document:
+    includes:
+      in_header: ["../../sty/galaaz.sty"]
+    number_sections: yes
+---
+\end{verbatim}
+
+\section{Conclusion}\label{conclusion}
+
+\section{Installing gKnit}\label{installing-gknit}
+
+\subsection{Prerequisites}\label{prerequisites}
+
+\begin{itemize}
+\tightlist
+\item
+  GraalVM (\textgreater{}= rc7)
+\item
+  TruffleRuby
+\item
+  FastR
+\end{itemize}
+
+The following R packages will be automatically installed when necessary,
+but could be installed prior to using gKnit if desired:
+
+\begin{itemize}
+\tightlist
+\item
+  ggplot2
+\item
+  gridExtra
+\item
+  knitr
+\end{itemize}
+
+Installation of R packages requires a development environment and can be
+time consuming. In Linux, the gnu compiler and tools should be enough. I
+am not sure what is needed on the Mac.
+
+\subsection{Preparation}\label{preparation}
+
+\begin{itemize}
+\tightlist
+\item
+  gem install galaaz
+\end{itemize}
+
+\subsection{Usage}\label{usage}
+
+\begin{itemize}
+\tightlist
+\item
+  gknit {[}filename{]}
+\end{itemize}
+
+
+\end{document}