{"id":3896,"date":"2020-08-10T21:42:29","date_gmt":"2020-08-10T21:42:29","guid":{"rendered":"https:\/\/mribeirodantas.xyz\/blog\/?p=3896"},"modified":"2025-01-31T04:37:50","modified_gmt":"2025-01-31T02:37:50","slug":"continuous-machine-learning","status":"publish","type":"post","link":"https:\/\/mribeirodantas.xyz\/blog\/index.php\/2020\/08\/10\/continuous-machine-learning\/","title":{"rendered":"Continuous Machine Learning – Part I"},"content":{"rendered":"Reading time: <\/span> 9<\/span> minutes<\/b><\/span><\/span>\n
\"\"
Image by Taras Tymoshchuck<\/a> from here<\/a>.<\/figcaption><\/figure>\n\n\n\n

This is a 3 part series about Continuous Machine Learning. You can check Part II here<\/a> and Part III here.<\/p>\n\n\n\n

What is it?<\/h2>\n\n\n\n

Continuous Machine Learning (CML<\/span>) follows the same concept of Continuous Integration and Continuous Delivery (CI\/CD)<\/a>, famous concepts in Software Engineering<\/a><\/span> \/ DevOps<\/a><\/span>, but applied to Machine Learning and Data Science projects.<\/p>\n\n\n\n

What is this post about?<\/h2>\n\n\n\n

I will cover a set of tools that can make your life as a Data Scientist much more interesting. We will use MIIC<\/a>, a network inference algorithm, to infer the network of a famous dataset (alarm from bnlearn<\/a>). We will then use (1) git<\/a> to track our code, (2) DVC<\/a> to track our dataset, outputs and pipeline, (3) we will use GitHub<\/a> as a git remote and (4) Google Drive<\/a> as a DVC remote. I’ve written a tutorial on managing Data Science projects with DVC, so if you’re interested on it open a tab here<\/a> to check it later.<\/p>\n\n\n\n\n\n\n\n

The first thing is that I don’t really like having to go to the GitHub website all the time, so I will also introduce you to gh<\/a>, GitHub’s official command line application. We will also use CML<\/span><\/a>, an open-source library for implementing continuous integration & delivery (CI\/CD) in machine learning projects, that will link git, DVC and GitHub Actions. The idea is that every time you do something in your repository, some actions will be triggered and executed by GitHub Actions in their computing infrastructure (They call it GitHub Runner, though it’s just a virtual machine. See more about it here<\/a>). One example would be using branches as experiments in your ML project, such as several inferences of the same algorithm but changing some parameters. Every time you commit changing a parameter and push, a report would be presented to make it easier (and beautiful) for you to compare the results with the different parameters.<\/p>\n\n\n\n

Time to start.<\/h2>\n\n\n\n

Let’s create our repository on GitHub and make a local copy of it. From the command line! (Instructions here<\/a> to install gh).<\/p>\n\n\n

\n\t\t\t\t
mkdir $HOME\/dev\r\ncd dev\r\ngh repo create dvc-miic-CML<\/span> -d 'GitHub repo to play with DVC, MIIC and CML<\/span>' --public<\/pre>\n\t\t\t<\/div>\n\n\n\n
You will be asked if you want to create a local copy of this repository. If you say no, you will have to clone the repository later, so reply Y<\/strong> and press enter. After that, enter the directory.<\/p>\n\n\n
\n\t\t\t\t
cd dvc-miic-CML<\/span><\/pre>\n\t\t\t<\/div>\n\n\n\n
Let’s create a README file so that we can describe the purpose of the repository. In GitHub, this is usually a file named README.md written in Markdown format<\/a>.<\/p>\n\n\n
\n\t\t\t\t
echo '# DVC-MIIC-CML<\/span>' > README.md\r\necho 'This is a sample repository for testing DVC, MIIC and CML<\/span> in GitHub.' >> README.md\r\necho 'The analyses will be performed using [MIIC](https:\/\/github.com\/miicTeam\/miic_R_package) to infer the network from the [alarm dataset](https:\/\/rdrr.io\/cran\/bnlearn\/man\/alarm.html).' >> README.md<\/pre>\n\t\t\t<\/div>\n\n\n\n
We will also download a license file (GNU GPLv3) from the GNU website<\/a> and have it named as LICENSE, as it is commonly done in GitHub.<\/p>\n\n\n
\n\t\t\t\t
wget -c https:\/\/www.gnu.org\/licenses\/gpl-3.0.txt -O LICENSE<\/pre>\n\t\t\t<\/div>\n\n\n\n
We will then add our two new files to the index of our git repository with the git add<\/em> command and then commit to the repository, that is, save a snapshot of our local repository. Afterwards, we will push our modifications to GitHub to make sure anyone can see the most up to date version of our repository. Since this is the first time we’re pushing, we will need to tell git what’s the default branch to push. We do that with the –set-upstream<\/em> parameter. In the future, when we want to push to the default branch, we can just type git push<\/em>.<\/p>\n\n\n
\n\t\t\t\t
# The dot when provided to git add means everything in the current folder\r\ngit add .\r\ngit commit -m 'Initial commit'\r\ngit push --set-upstream origin master<\/pre>\n\t\t\t<\/div>\n\n\n\n
You can check your repository at GitHub now. It should be updated! Mine is<\/a>. Git is not supposed to track data, output files (metrics files, plots, reports) or pipelines. That’s where DVC fits in. Let’s start by tracking the alarm dataset. You can download it from MIIC official website clicking here<\/a>. In the command line, that’s what we would do:<\/p>\n\n\n
\n\t\t\t\t
wget -c https:\/\/miic.curie.fr\/datasets\/alarm1000samples.txt -O alarm.tsv<\/pre>\n\t\t\t<\/div>\n\n\n\n
I don’t really like when git repositories are just a bunch of files thrown at the root folder, so let’s make it a bit more organized.<\/p>\n\n\n
\n\t\t\t\t
mkdir data\r\nmv alarm.tsv data\/<\/pre>\n\t\t\t<\/div>\n\n\n\n
DVC enters the scene<\/h2>\n\n\n\n
If you type git status<\/em>, you will see that the folder is untracked, which is a bit annoying since (a) git is not supposed to track data and (b) you do not want that either. One of the things that DVC does, after being told to track files, is to tell git to ignore such files. After all, DVC will be taking care of them! Before telling DVC what to track, though, you must tell DVC you want it to work in this repository. Just like you would normally do with a new git repository without the help of gh (git init<\/em>), you do with DVC. Let’s do this and then tell DVC to track our dataset. Instructions on DVC installation can be found here<\/a>.<\/p>\n\n\n
\n\t\t\t\t
dvc init\r\ndvc add data\/alarm.tsv<\/pre>\n\t\t\t<\/div>\n\n\n\n
Some files will be created by DVC. These meta data files must be tracked by git, so let’s just add everything new to the index and commit it. Our dataset won’t be added because DVC added it to .gitignore, a hidden file used by git for this purpose: what to ignore.<\/p>\n\n\n
\n\t\t\t\t
git add .\r\ngit commit -m 'Initiates DVC and asks it to track alarm dataset'<\/pre>\n\t\t\t<\/div>\n\n\n\n
Just to make sure that the workflow of git is clear to you, you don’t have to push every time you commit. We won’t push now, for example (though we could). Just like GitHub is a git remote, you can also have a DVC remote. It can be Dropbox, an Amazon S3 bucket, Google Drive or even a folder in your computer or in your external disk. For simplicity here, let’s use Google Drive.<\/p>\n\n\n\n
I went to the Google Drive website, logged with my account, and created at the root of my drive a new folder named dvc-miic-CML<\/span> example<\/em>. The URL is https:\/\/drive.google.com\/drive\/u\/1\/folders\/188CmpQIYqKOgvcgaLZOxz1GqlwTasv8c<\/a><\/strong><\/p>\n\n\n\n
What you need here is the last part after the folders\/<\/strong>, that is, 188CmpQIYqKOgvcgaLZOxz1GqlwTasv8c<\/strong>. Let’s set this as our DVC remote now with the following command:<\/p>\n\n\n
\n\t\t\t\t
dvc remote add -d myremote gdrive:\/\/188CmpQIYqKOgvcgaLZOxz1GqlwTasv8c<\/pre>\n\t\t\t<\/div>\n\n\n\n
The -d<\/strong> parameter is important to tell DVC that this is your default remote. Otherwise, it will ask you what remote you want to use whenever you run a command that will do something based on a remote. We used git push<\/em> to push to git. Can you guess what command we should use to push to our DVC remote at Google Drive? I’m sure you guessed it right!<\/p>\n\n\n
\n\t\t\t\t
dvc push<\/pre>\n\t\t\t<\/div>\n\n\n\n
If you check your folder in Google Drive you will see it is no longer empty. You can’t really understand what’s there, but take my word for it: DVC knows how to interpret it \ud83d\ude1b . As an habit, you type git status<\/em> and you realize something changed in your repository. Wait, what!?<\/em> By adding a default remote, the DVC configuration file was changed. You could git add<\/code> the folder and git commit<\/code> it but for didactic reasons I will do something else: I will amend it to the last commit, and by doing so, update the commit message. Amending is useful when you committed something but forgot to add something, or you decided that your last commit message wasn’t that good. So you change your last commit, instead of doing a new one!<\/p>\n\n\n
\n\t\t\t\t
git add .\r\ngit commit --amend -m 'Initiates DVC, sets the default remote and asks it to track alarm dataset'<\/pre>\n\t\t\t<\/div>\n\n\n\n
Ok, let’s push now.<\/p>\n\n\n
\n\t\t\t\t
git push<\/pre>\n\t\t\t<\/div>\n\n\n\n
The GitHub page for your repository should look like this<\/a>. You may wonder why there are two files in your data folder since I told you git won’t be used to track data. One of the files is .gitignore, to make sure git won’t annoy you saying that the dataset file is not tracked, when it actually is tracked [by DVC]. The .dvc file is a meta data file used by DVC and it contains a hash built out of the content of the dataset. That’s how DVC knows if the dataset changed, because the hash will change.<\/p>\n\n\n\n
DVC Note<\/h2>\n\n\n\n
If someone is interested in this repository (maybe you are), they would initially do just like any other GitHub repository: They would clone it!<\/p>\n\n\n
\n\t\t\t\t
git clone https:\/\/github.com\/mribeirodantas\/dvc-miic-CML<\/span>.git\r\ncd dvc-miic-CML<\/span><\/pre>\n\t\t\t<\/div>\n\n\n\n
By checking the data folder with ls data<\/code>, you will realize the dataset is not there. Well, of course it is not there, right? You only cloned the git repository. Let’s use dvc pull<\/em> to pull what DVC is tracking for this repository.<\/p>\n\n\n
\n\t\t\t\t
dvc pull<\/pre>\n\t\t\t<\/div>\n\n\n\n
Now it’s there \ud83d\ude42 . Let’s start writing our network inference script. We will use MIIC (Multivariate information-based inductive causation) for that. Create a file named infer_network.R<\/code> with the content below:<\/p>\n\n\n
\n\t\t\t\t
library(miic)\r\nalarm_dataset <- read.table('data\/alarm.tsv', header = TRUE)\r\nres <- miic(input_data = alarm_dataset)\r\ntotal_edges <- nrow(res$all.edges.summary)\r\nretained_edges <- nrow(res$all.edges.summary[res$all.edges.summary$type == 'P', ])\r\nratio_edges <- paste0('Ratio of retained edges: ', retained_edges\/total_edges)\r\nwrite.table(ratio_edges, file = 'metrics.txt', col.names = FALSE, row.names = FALSE)<\/pre>\n\t\t\t<\/div>\n\n\n\n
This code loads the miic R package, reads the dataset into the R environment, runs miic to infer the network and calculates the ratio of retained edges by the number of possible edges. Then, the ratio is saved to a file named metrics.txt.<\/p>\n\n\n\n
GitHub Actions<\/h2>\n\n\n\n
Now it’s time to start playing with GitHub Actions to make CML<\/span> work for us. Every time we push a new commit to the repository, the model will be rebuilt and our metrics recalculated.<\/p>\n\n\n\n
In order to use GitHub Actions, we need to create a special file in a special folder. The path from within your git repository is: .github\/workflows<\/strong><\/p>\n\n\n\n
Inside the folder, you have to create your GitHub Action file. The name is not important, but it must be a file in YAML format<\/a>. Let’s create a file named CML<\/span>.yaml<\/code> inside the path mentioned above.<\/p>\n\n\n
\n\t\t\t\t
mkdir -p .github\/workflows\r\ncd .github\/workflows<\/pre>\n\t\t\t<\/div>\n\n\n\n
Then, create a file named CML<\/span>.yaml<\/code> and put the code below inside it. This asks for a machine running the latest version of Ubuntu, sets up an R environment, checks out the current git repository, installs MIIC, DVC, their dependencies, dvc pull<\/code> our dataset, calls the infer_network.R<\/code> script that will save the metrics to a file in the end, and then output it.<\/p>\n\n\n
\n\t\t\t\t
name: dvc-CML<\/span>-miic\r\non: [push]\r\njobs:\r\n  run:\r\n    runs-on: [ubuntu-latest]\r\n    steps:\r\n      - uses: r-lib\/actions\/setup-r@master\r\n        with:\r\n          version: '3.6.1'\r\n      - uses: actions\/checkout@v2\r\n      - name: cml_run\r\n        env:\r\n          repo_token: ${{ secrets.GITHUB_TOKEN }}\r\n          GDRIVE_CREDENTIALS_DATA: ${{ secrets.GDRIVE_CREDENTIALS_DATA }}\r\n        run: |\r\n          # Install miic and dependencies\r\n          wget -c https:\/\/github.com\/miicTeam\/miic_R_package\/archive\/v1.4.2.tar.gz\r\n          tar -xvzf v1.4.2.tar.gz\r\n          cd miic_R_package-1.4.2\r\n          R --silent -e "install.packages(c(\\"igraph\\", \\"ppcor\\", \\"scales\\", \\"Rcpp\\"))"\r\n          R CMD INSTALL . --preclean\r\n          cd ..\r\n          # Install Python packages\r\n          pip install --upgrade pip\r\n          pip install wheel\r\n          pip install PyDrive2==1.6.0 --use-feature=2020-resolver\r\n          # Install DVC\r\n          wget -c https:\/\/github.com\/iterative\/dvc\/releases\/download\/1.4.0\/dvc_1.4.0_amd64.deb\r\n          sudo apt install .\/dvc_1.4.0_amd64.deb\r\n          # Run DVC\r\n          dvc pull\r\n          Rscript infer_network.R\r\n          # Write your CML<\/span> report\r\n          echo "MODEL METRICS"\r\n          cat metrics.txt<\/pre>\n\t\t\t<\/div>\n\n\n\n
Instead of comitting this to the master (default) branch, we will create an experiment branch. That’s how you should use DVC! We will analyze the raw version of the alarm dataset, no pre-processing, so I will call this branch raw_alarm_dataset.<\/p>\n\n\n\n
You have used dvc pull<\/code> already, so you authenticated your machine with Google Drive. Create a GitHub secret<\/a> with the content of the file .dvc\/tmp\/gdrive-user-credentials.json<\/code> and name it GDRIVE_CREDENTIALS_DATA.<\/p>\n\n\n
\n\t\t\t\t
git checkout -b raw_alarm_dataset\r\n# infer_network.R is not in this folder, therefore `git add .` wouldn't\r\n# add it to the index of your git repository. -A adds everything.\r\ngit add -A\r\ngit commit -m 'Infers alarm network with MIIC and default parameters'\r\ngit push origin raw_alarm_dataset\r\ngh pr create --title 'Network inference of alarm dataset'<\/pre>\n\t\t\t<\/div>\n\n\n\n
Now, go to GitHub and check what’s happening<\/a>. If everything goes according to plan, you will see something like the image below when the check is over.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Well… You got your metrics printed out in the checks log file. Cool, but you probably agree with me that we should expect something more elegant, right? Hehe `^^<\/p>\n\n\n\n
Let’s add some lines to our infer_network.R<\/code> script to make it plot the network, and then let’s change the last part to make use of CML<\/span> functionalities. The new infer_network.R<\/code> should look like:<\/p>\n\n\n
\n\t\t\t\t
library(miic)\r\nalarm_dataset <- read.table('data\/alarm.tsv', header = TRUE)\r\nres <- miic(input_data = alarm_dataset)\r\ntotal_edges <- nrow(res$all.edges.summary)\r\nretained_edges <- nrow(res$all.edges.summary[res$all.edges.summary$type == 'P', ])\r\nratio_edges <- paste0('Ratio of retained edges: ', retained_edges\/total_edges)\r\nwrite.table(ratio_edges, file = 'metrics.txt', col.names = FALSE, row.names = FALSE)\r\n# Plot network\r\npng(file='network_diagram.png')\r\nmiic.plot(res)\r\ndev.off()<\/pre>\n\t\t\t<\/div>\n\n\n\n
And the new CML<\/span>.yaml<\/code> file should look like the code below. The new thing now is that we’re also installing CML<\/span> and making use of it.<\/p>\n\n\n
\n\t\t\t\t
name: dvc-CML<\/span>-miic\r\non: [push]\r\njobs:\r\n  run:\r\n    runs-on: [ubuntu-latest]\r\n    steps:\r\n      - uses: r-lib\/actions\/setup-r@master\r\n        with:\r\n          version: '3.6.1'\r\n      - uses: actions\/checkout@v2\r\n      - name: cml_run\r\n        env:\r\n          repo_token: ${{ secrets.GITHUB_TOKEN }}\r\n          GDRIVE_CREDENTIALS_DATA: ${{ secrets.GDRIVE_CREDENTIALS_DATA }}\r\n        run: |\r\n\r\n          # Install miic and dependencies\r\n          wget -c https:\/\/github.com\/miicTeam\/miic_R_package\/archive\/v1.4.2.tar.gz\r\n          tar -xvzf v1.4.2.tar.gz\r\n          cd miic_R_package-1.4.2\r\n          R --silent -e "install.packages(c(\\"igraph\\", \\"ppcor\\", \\"scales\\", \\"Rcpp\\"))"\r\n          R CMD INSTALL . --preclean\r\n          cd ..\r\n          # Install Python packages\r\n          pip install --upgrade pip\r\n          pip install wheel\r\n          pip install PyDrive2==1.6.0 --use-feature=2020-resolver\r\n          # Install DVC\r\n          wget -c https:\/\/github.com\/iterative\/dvc\/releases\/download\/1.4.0\/dvc_1.4.0_amd64.deb\r\n          sudo apt install .\/dvc_1.4.0_amd64.deb\r\n          # Run DVC\r\n          dvc pull\r\n          Rscript infer_network.R\r\n\r\n          # Install CML<\/span>\r\n          npm init --yes\r\n          npm i @dvcorg\/CML<\/span>@latest\r\n          # Write your CML<\/span> report\r\n          echo "## Model Metrics" > report.md\r\n          cat metrics.txt >> report.md\r\n          echo "## Data visualization" >> report.md\r\n          npx CML<\/span>-publish network_diagram.png --md >> report.md\r\n          npx CML<\/span>-send-comment report.md<\/pre>\n\t\t\t<\/div>\n\n\n\n
Let’s commit.<\/p>\n\n\n
\n\t\t\t\t
git add .\r\ngit commit -m 'Uses CML<\/span> to improve PR feedback'\r\ngit push origin raw_alarm_dataset<\/pre>\n\t\t\t<\/div>\n\n\n\n
Now, right after the checks are done, you should have an automatic comment with your report like in the figure below.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Let’s say that I think too many edges have been removed and maybe the network is not consistent. I will change the infer_network.R<\/code> script to make MIIC look for a consistent<\/a> network. The third line now looks like:<\/p>\n\n\n
\n\t\t\t\t
res <- miic(input_data = alarm_dataset, consistent='orientation')<\/pre>\n\t\t\t<\/div>\n\n\n\n
And commit.<\/p>\n\n\n
\n\t\t\t\t
git add .\r\ngit commit -m 'Makes network consistent'\r\ngit push origin raw_alarm_dataset<\/pre>\n\t\t\t<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n
So now I think it’s right and I should approve the pull request \ud83d\ude42 . I could do it clicking on the green \u201cMerge pull request\u201d button or I could use gh<\/code> again, GitHub’s official command line application.<\/p>\n\n\n
\n\t\t\t\t
gh pr merge 1<\/pre>\n\t\t\t<\/div>\n\n\n\n
It will ask you two questions. I chose to create a merge commit and to not remove the branch, be it locally or at GitHub. To go back to the master branch, you should do:<\/p>\n\n\n
\n\t\t\t\t
git checkout master<\/pre>\n\t\t\t<\/div>\n\n\n\n
Using Docker containers<\/h2>\n\n\n\n
You probably noticed it takes a while to do the checks and depending on how many things you want to install, it can take very long. One way out of this situation is by using a docker container that already has your dependencies installed. The way we’ve been doing it so far is ready for you to use your containers, after all, I’m installing CML<\/span> manually. If you don’t want to use a container of yours, but don’t want either to download and install CML<\/span> at every check, you can use CML<\/span>’s official docker container.<\/p>\n\n\n\n
Since we merged a pull request, our remote (GitHub) is different from our local repository. To update our local repository, let’s run git pull<\/code>, and then create a new branch.<\/p>\n\n\n
\n\t\t\t\t
git pull\r\ngit checkout -b CML<\/span>_container<\/pre>\n\t\t\t<\/div>\n\n\n\n
Change your CML<\/span>.yaml<\/code> to the code below.<\/p>\n\n\n
\n\t\t\t\t
name: dvc-CML<\/span>-miic\r\non: [push]\r\njobs:\r\n  run:\r\n    runs-on: [ubuntu-latest]\r\n    container: docker:\/\/dvcorg\/cml\r\n    steps:\r\n      - uses: actions\/checkout@v2\r\n        \r\n      - uses: r-lib\/actions\/setup-r@master\r\n        with:\r\n          version: '3.6.1'\r\n\r\n      - name: cml_run\r\n        env:\r\n          repo_token: ${{ secrets.GITHUB_TOKEN }}\r\n          GDRIVE_CREDENTIALS_DATA: ${{ secrets.GDRIVE_CREDENTIALS_DATA }}\r\n        run: |\r\n          # Install miic and dependencies\r\n          wget -c https:\/\/github.com\/miicTeam\/miic_R_package\/archive\/v1.4.2.tar.gz\r\n          tar -xvzf v1.4.2.tar.gz\r\n          cd miic_R_package-1.4.2\r\n          R --silent -e "install.packages(c(\\"igraph\\", \\"ppcor\\", \\"scales\\", \\"Rcpp\\"))"\r\n          R CMD INSTALL . --preclean\r\n          cd ..\r\n\r\n          # Run DVC\r\n          dvc pull\r\n          Rscript infer_network.R\r\n\r\n          # Write your CML<\/span> report\r\n          echo "## Model Metrics" > report.md\r\n          cat metrics.txt >> report.md\r\n          echo "## Data visualization" >> report.md\r\n          CML<\/span>-publish network_diagram.png --md >> report.md\r\n          CML<\/span>-send-comment report.md<\/pre>\n\t\t\t<\/div>\n\n\n\n
Let’s add the changed file, commit it, push and create a Pull Request (PR).<\/p>\n\n\n
\n\t\t\t\t
git add .\r\ngit commit -m 'Makes use of CML<\/span> container'\r\ngit push origin CML<\/span>_container\r\ngh pr create --title 'Use CML<\/span> container'<\/pre>\n\t\t\t<\/div>\n\n\n\n
Everything should have run fine, like in here<\/a>. You can merge the pull request and then git pull<\/code> to update your local copy.<\/p>\n\n\n
\n\t\t\t\t
gh pr merge 2\r\ngit pull<\/pre>\n\t\t\t<\/div>\n\n\n\n
What else?<\/h2>\n\n\n\n
DVC is not limited to data tracking. We could also track our pipeline, including output files such as the images that our infer_network.R<\/code> script plotted. Imagine that we could have some code for preprocessing that would deliver a preprocessed dataset to the infer_network.R<\/code> script that would generate the image with the network. Instead of running all these scripts (and we can easily think of scenarios that are much more complicated), we can use dvc to create a pipeline and a simple command (dvc repro<\/code>) in our GitHub action file would be enough to reproduce our whole pipeline.<\/p>\n\n\n\n
Besides, instead of installing a bunch of the same things (R, DVC, CML<\/span>…) every time we push to the repository, we could have a Docker container with these things already installed. This could save us some time :-). In our case here, for example, downloading, compiling and installing MIIC takes a few minutes that could be spared if it was already installed in a Docker container. For our simple example, the time to download\/setup the docker container may not make it worth to use it, but when complexity and dependencies increase, the benefits become more evident.<\/p>\n\n\n\n
That’s it for today folks! \ud83d\ude09<\/p>\n\n\n\n
You would not be reading this post if it wasn’t for Elle O’Brien<\/a>, who told me so many things about CML<\/span> + presentations and examples, and David Ortega<\/a> who helped me setting up the R environment within the CML<\/span> docker container.<\/p>\n