diff --git a/README.md b/README.md
index e4e8fc45e19361c9e225afb95c44fd2f1a34c9a0..9cd759b2b8f3691d6b1648d91966ca2f49348b3c 100644
--- a/README.md
+++ b/README.md
@@ -12,14 +12,13 @@ This repository contains the materials presented in the paper 'An approach for d
 <a href="https://liris.cnrs.fr/page-membre/mihaela-scuturici">Mihaela Scuturici</a>,
 <a href="https://liris.cnrs.fr/page-membre/serge-miguet">Serge Miguet</a>
 
+<div style="text-align:center"><img style="margin-right: 20px" src="assets/fig3.png" alt="Pipeline" height="75" width="160"/>
+
 # Table of content
 - [Overview](#description)
 - [Citation](#citation)
 - [Acknowledgements](#acknowledgments)
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
 ## Installation
 Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.