Skip to content

Latest commit

 

History

History
46 lines (34 loc) · 4.23 KB

README.md

File metadata and controls

46 lines (34 loc) · 4.23 KB

About

This is the back-end component of the Fractalis project. It is a computational node that is responsible for the MicroETL process and the execution of analytical tasks. See https://fractalis.lcsb.uni.lu/

Demo

Please have a look at this playlist to see a demo of the visual aspects of Fractalis: Playlist.

Installation (Docker)

The easiest and most convenient way to deploy Fractalis is using Docker. All necessary information can be found here.

Installation (Manual)

If you do not want to use docker or want a higher level of control of the several components, that's fine. In fact it isn't difficult to setup Fractalis manually:

  • Install and run Redis, which is available on most Linux distributions. This instance must be accessible by the web service and the workers.
  • Install and run RabbitMQ, which is available on most Linux distributions. This instance must be accessible by the web service and the workers.
  • Install Fractalis via pip3 install fractalis. Please note that Fractalis requires Python3.4 or higher. This must be installed on all machines that will run the web service or the workers.
  • Install required all required R packages. We won't list these packages excplicitely, as they can change frequently. Please refer instead to the Dockerfile, which is always up-to-date, as a new version of Fractalis is only released when the Docker image passes all tests. This must be installed on all machines that will run the web service or the workers.
  • Run and expose the Fractalis web service with whatever tools you want. We recommend gunicorn and nginx, but others should work, too.
  • Run the celery workers on any machine that you want within the same network. (For a simple setup this can be the very same machine that the web service runs on).

Note: The docker-compose.yml describes how the different services are started and how they connect with each other.

Configuration

Use the environment variable FRACTALIS_CONFIG to define the configuration file path. This variable must be a) a valid python file (.py) and b) be available on all instances that host a Fractalis web service or a Fractalis worker.

Tip: Use the default settings as an example for your own configuration file. Please note, that all this files combines Flask settings, Celery settings, and Fractalis settings, which are all listed and documented within this file. Please don't overwrite default settings if you don't know what you are doing. This might have severe implications for security or might cause Fractalis to not work correctly.

Add new analytics

This paragraph only describes how to add the statistical analysis part in R or Python. For the visualisation please refer to the Fractal.js repository. Adding new scripts to Fractalis is a matter of inheriting from the AnalyticTask class and well... knowing how to write Python and R scripts. There are a few things that are enforced by the parent class, such as a task name and the existence of a main method, which is communicated to the developer by readable error messages. Implementing those will result in a distributable task without any required knowledge of the surrounding frameworks. For an example please have a look at the correlation analysis script.

Input to the main method are either the parameters submitted by the client or, in the case of special data ids ("$123654789$"), the data frame associated with he data id.

Output of the main method must be JSON serializable. The content however is up to the developer.

Add support for new services

Please refer to this document.

Citation

https://academic.oup.com/gigascience/article/7/9/giy109/5082751