Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/IHaskell/ihaskell-notebook

IHaskell image for Jupyter Docker Stacks
https://github.com/IHaskell/ihaskell-notebook

haskell jupyter

Last synced: about 2 months ago
JSON representation

IHaskell image for Jupyter Docker Stacks

Awesome Lists containing this project

README 

        
# ihaskell-notebook



[![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/IHaskell/learn-you-a-haskell-notebook/master?urlpath=lab/tree/ihaskell_examples/ihaskell/IHaskell.ipynb)



A [Community Jupyter Docker Stacks](https://jupyter-docker-stacks.readthedocs.io/en/latest/using/selecting.html#community-stacks) image. Provides the Jupyter [IHaskell](https://github.com/IHaskell/IHaskell) kernel in a Docker image which composes well with other Jupyter Docker Stacks. Docker images are [published on the Github container registry.](https://github.com/IHaskell/ihaskell-notebook/pkgs/container/ihaskell-notebook)



`docker run` the latest image right now with the following shell command, then open [http://localhost:8888](http://localhost:8888) to try out the Jupyter notebook. Your current working directory on your host computer will be mounted at __Home / pwd__ in JupyterLab.



```bash

docker run --rm -p 8888:8888 -v $PWD:/home/jovyan/pwd --name ihaskell_notebook ghcr.io/ihaskell/ihaskell-notebook:master jupyter lab --ServerApp.token=''

```



Or with `podman`:



```bash

podman run --privileged --userns=keep-id --rm -p 8888:8888 -v $PWD:/home/jovyan/pwd --name ihaskell_notebook ghcr.io/ihaskell/ihaskell-notebook:master jupyter lab --ServerApp.token=''

```



## Image structure



This image includes:



* [__JupyterLab 3__](https://jupyterlab.readthedocs.io/en/stable/)

* [__IHaskell__](https://github.com/IHaskell/IHaskell) Jupyter kernel

* [__jupyterlab-ihaskell__](https://github.com/IHaskell/IHaskell/tree/master/jupyterlab-ihaskell) JupyterLab extension for Haskell syntax highlighting in notebooks

* Haskell libraries for instances of [IHaskell.Display](https://www.stackage.org/haddock/lts-12.26/ihaskell-0.9.1.0/IHaskell-Display.html)

  * __ihaskell-aeson__ for [Aeson](http://hackage.haskell.org/package/aeson) JSON display

  * __ihaskell-blaze__ for [Blaze](http://hackage.haskell.org/package/blaze-html) HTML display

  * __ihaskell-gnuplot__ for [gnuplot](http://www.gnuplot.info/) graphing utility

  * __ihaskell-juicypixels__ for [JuicyPixels](http://hackage.haskell.org/package/JuicyPixels) image display

  * __ihaskell-plot__ for [plots](https://hackage.haskell.org/package/plots) diagrams-based plotting library

  * __ihaskell-graphviz__ for [Graphviz](https://www.graphviz.org/) graph visualization

  * __ihaskell-diagrams__ for [diagrams](https://archives.haskell.org/projects.haskell.org/diagrams/) language for creating vector graphics

  * __ihaskell-charts__ for [Chart](https://github.com/timbod7/haskell-chart/wiki) rendering 2D charts

  * __ihaskell-hatex__ for [HaTeX](http://daniel-diaz.github.io/projects/hatex/hatex-guide.html) LaTeX

  * __ihaskell-widgets__ for [Widgets](https://github.com/IHaskell/IHaskell/tree/master/ihaskell-display/ihaskell-widgets) interactive user-interface controls

  * [__DougBurke/ihaskell-hvega__](https://github.com/DougBurke/hvega) for [Vega/Vega-Lite rendering, natively supported by JupyterLab](https://jupyterlab.readthedocs.io/en/stable/user/file_formats.html#vega-lite)

* [__Haskell Stack__](https://docs.haskellstack.org/en/stable/README/) package manager, with [Glasgow Haskell Compiler](https://www.haskell.org/ghc/).



The image is configured with the [common features of Jupyter Docker Stacks](https://jupyter-docker-stacks.readthedocs.io/en/latest/using/common.html).



To ensure that this image composes well with any authentication and storage configuration

(for example [SystemUserSpawner](https://github.com/jupyterhub/dockerspawner#systemuserspawner))

or notebook directory structure, we try to avoid installing anything in the Docker image in `/home/jovyan`.



This image is made with JupyterLab in mind, but it works well for classic notebooks.



Example notebooks are collected together in the container at `/home/jovyan/ihaskell_examples`.



## `IHaskell.Display`



Some libraries for instances of [`IHaskell.Display`](https://www.stackage.org/haddock/lts-12.26/ihaskell-0.9.1.0/IHaskell-Display.html) are pre-installed in the JupyterLab container.



The installed libraries mostly come from  mostly from [`IHaskell/ihaskell-display`](https://github.com/gibiansky/IHaskell/tree/master/ihaskell-display), and are installed if they appeared to be working at the time the JupyterLab Docker image was built. You can try to install the other `IHaskell/ihaskell-display` libraries, and they will be built from the `/opt/IHaskell` source in the container.



```bash

stack build ihaskell-magic

```



See the Stack *global project* `/opt/stack/global-project/stack.yaml` for information about the `/opt/IHaskell` source in the container.



You can see which libraries are installed by running `ghc-pkg`:



```bash

stack exec ghc-pkg -- list | grep ihaskell

    ihaskell-0.9.1.0

    ihaskell-aeson-0.3.0.1

    ihaskell-blaze-0.3.0.1

    ihaskell-gnuplot-0.1.0.1

    ihaskell-hvega-0.2.0.0

    ihaskell-juicypixels-1.1.0.1

    ...

```



## Stack *global project*



The `ihaskell` executable, the `ihaskell` library, the `ghc-parser` library,

and the `ipython-kernel` library are built and installed at the level

of the [Stack *global project*](https://docs.haskellstack.org/en/stable/yaml_configuration/#yaml-configuration) in `/opt/stack/global-project/stack.yaml`.

This design choice was discussed in [IHaskell issue #715](https://github.com/gibiansky/IHaskell/issues/715#issuecomment-338580095).



This means that the `ihaskell` environment is available for all users in any directory mounted in the

Docker container, so you can __save and run `.ipynb` notebook files in any directory__, which is one of the main advantage of this IHaskell Docker image.

The present working directory (`PWD`) of a Jupyter notebook is the always the directory in which the notebook

is saved.



The Stack *global project* `resolver`

is determined by the IHaskell project `resolver`, and all included Haskell

libraries are built using that Stack `resolver`.



### Installing Haskell packages



You can install packages with `stack build`. For example, if you encounter a notebook error for a missing `hmatrix` package,



```

:1:1: error:

   Could not find module ‘Numeric.LinearAlgebra’

   Use -v to see a list of the files searched for.

```



then you can install the missing `hmatrix` package from the terminal in your container:



```bash

stack build hmatrix

```



Or, in a notebook, you can use the [GHCi-style shell commands](https://github.com/gibiansky/IHaskell/wiki#shelling-out):



```

:!stack build hmatrix

```



And then ⭮ restart your IHaskell kernel.



You can use this technique to create a list of package dependencies at the top of a notebook:



```

:!stack build hmatrix

import Numeric.LinearAlgebra

ident 3

```



~~~

(3><3)

 [ 1.0, 0.0, 0.0

 , 0.0, 1.0, 0.0

 , 0.0, 0.0, 1.0 ]

~~~



#### Installing Haskell packages caveats



1. You can only install packages from the

   [Stackage](https://www.stackage.org/) snapshot from the Stack *global project*

   [`/opt/stack/global-project/stack.yaml`](global-project.stack.yaml) `resolver`.

2. The first time you run the notebook the packages will be installed, but

   then the kernel will not load them. You must ⭮ restart the

   kernel to load the newly-installed packages.



## Local project modules



You can add supporting modules of `.hs` files in the same directory where

your `.ipynb` notebook file is stored.



If you create a file `MyModule.hs` with the contents



```haskell

module MyModule where

support x = x + x

```



Then you can use the `support` function in your `.ipynb` notebook like this



```haskell

:load MyModule

import MyModule (support)

```



## System GHC



The GHC version specified by the IHaskell Stack `resolver` is also installed

in the container at the system level, that is, on the executable `PATH`.



## Building and running the Dockerfile locally



```

make build

make up

```



Open http://localhost:8888/



## Composition with Docker Stacks



Rebase the IHaskell `Dockerfile` on top of another Jupyter Docker Stack image, for example the

[`scipy-notebook`](https://jupyter-docker-stacks.readthedocs.io/en/latest/using/selecting.html#jupyter-scipy-notebook):



```

docker build --build-arg BASE_CONTAINER=jupyter/scipy-notebook --rm --force-rm -t ihaskell_scipy_notebook:latest .

```



## References, Links, Credits



[IHaskell on Hackage](http://hackage.haskell.org/package/ihaskell)



[IHaskell on Stackage](https://www.stackage.org/package/ihaskell/snapshots)



[IHaskell Wiki with Exemplary IHaskell Notebooks](https://github.com/gibiansky/IHaskell/wiki)



[Learn You a Haskell for Great Good, Jupyter adaptation](https://github.com/IHaskell/learn-you-a-haskell-notebook)



[When Is Haskell More Useful Than R Or Python In Data Science?](https://www.quora.com/What-are-some-use-cases-for-which-it-would-be-beneficial-to-use-Haskell-rather-than-R-or-Python-in-data-science) by [Tikhon Jelvis](https://github.com/TikhonJelvis)



[datahaskell.org](http://www.datahaskell.org/)



[tweag/jupyterWith Jupyter Nix build](https://github.com/tweag/jupyterWith)