No Description

at-robins 140b0cf0e9 [8] Added first pipeline definition 1 year ago
backend 39ed6b3087 [8] Added pipeline step variables 1 year ago
frontend 6bd6f4f0ae [8] Fixed tests 1 year ago
pipelines 140b0cf0e9 [8] Added first pipeline definition 1 year ago
testing_resources b3b3609a9e [8] Added variables for pipeline steps 1 year ago
.gitignore 6ee1a2d9bd [0] Sample application setup 2 years ago
LICENSE 71b98eea85 Initial commit 2 years ago
README.md d2d4f205f7 [8] Added pipeline loading on application startup 1 year ago

README.md

MriSequencingPipeline

Design philosophy

This sequencing pipeline is intended as a simple, streamlined, well documented and tested solution for common sequencing approaches. Since transformation and analysis of sequencing data is typically a time and resource consuming task, the main focus is not placed on scalability of a centralised processing pipeline for e.g. a core facility. Rather a Docker image is provided to allow easy setup of the pipeline within a specific workgroup. Each image is thereby self-contained, so all processed data and associated information (database etc.) is stored within the respective container. While this severely limits the scalability it allows for an easy setup, documentation and improves general usability. For the same reasons execution of pipelines themselves is not paralellised. Instead each pipeline step uses paralellisation whenever possible.

Architecture

Frontend

Vue.js with the Quasar framework is used for easy implementation of the frontend.

Backend

An actix-Rust-backend is used as a statically typed, fast and reliable backend.

Database

SQLite is used as it provides a simple, self-contained and fast database. Diesel is used for automated database migration.

Containerisation

Docker was selected as tool for running and managing containers due to its ease of use and widespread adoption.

Usage

TODO: Insert once the Docker image is created.

Enviroment variables

Also see backend/.env.

Variable Description
CONTEXT_FOLDER the context folder of the application where all relevant data is stored
DATABASE_URL the database location
LOG_LEVEL the minimum log level of the application (debug, info, warn, error)
PIPELINE_FOLDER the folder storing pipeline definitions
SERVER_ADDRESS the address of the server
SERVER_PORT the port of the server

Build (for developers)

Prerequisites:

# Install Rust.
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
# Install Node.
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo bash -
sudo apt update
sudo apt install nodejs
# Install the requirements for the openssl crate.
sudo apt install libssl-dev

Conventional release build:

cd backend
cargo build --release

Building for development:

cd backend
cargo build
cd ../frontend
npm install
npm run build

Run (for developers)

Prerequisites:

# Install SQLite and the Diesel dependency.
sudo apt install sqlite3 libsqlite3-dev
# Install Diesel.
cargo install diesel_cli --no-default-features --features sqlite
# Initialise the database.
cd backend
mkdir application # without the sub-folder Diesel will fail to create the database
diesel setup
# Install docker for containerisation of the pipeline.
sudo apt install docker.io

Running a release build:

cd backend
cargo run --release

Running for development:

cd backend
cargo run
cd ../frontend
npm run build:dev

Testing

Backend testing:

cd backend
cargo test

Frontend testing:

cd frontend
npm run test:unit