Skip to main content

should make things more reproducible

Project description

DBIS Pipeline

This pipline can be used to run analyses in a structured way, and stores configurations and results in a database.

Usage

the user writes a minimal plan file which contains only the following information:

  • "how do I get the data?", by providing a dataloader
  • "what to do with the data?", by providing a scikit pipeline
  • "how to process the result?", by providing result handlers.
  • "where to additionally store results?" by providing storage handlers.

Please have a look at the examples for more information.

CLI

We provide a dbispipeline-link tool that can be used to link datasets to the data directory. This ensures that datasets are linked in a consistent way even on different machines. The general process is as follows:

  1. Either in the dbispipeline.ini or as an argument in the cli call, one can define where in general datasets are stored on the local machine. For example, many datasets are available on /storage/nas3/datasets/text. In this case, this would be the value in the configuration:

    #dbispipeline.ini:
    [project]
    dataset_dir = /storage/nas3/datasets
    
  2. In a file data/links.yaml, one can define specific datasets that are used by the software. Thereby, the first path segment will be cut off (not sure why). For example, the following yaml file:

    ---
    datasets:
      - music/acousticbrainz
      - music/billboard
      - music/millionsongdataset
    

    would assume that a physical directory exists at /storage/nas3/datasets/music/billboard and after calling the script dbispipeline-link without parameters using the above configuration, the following symlinks will be created:

    data/acousticbrainz -> /storage/nas3/datasets/music/acousticbrainz
    data/billboard -> /storage/nas3/datasets/music/billboard
    data/millionsongdataset -> /storage/nas3/datasets/music/millionsongdataset
    

    The value of dataset_dir from the config can be overwritten in the cli script by using the -p option.

Requirements

  • python >= 3.6
  • a PostgreSQL database
  • an email server if you want to use notification emails

Installation

  1. Install dbispipeline in your python. We recommend using pipenv to keep your dependencies clean: pipenv install dbispipeline This call will install a virtual environment as well as all dependencies.
  2. Write your plan(s). See the example plan files for guidance.
  3. call pipenv run dp <yourplanfile.py>

Enjoy!

Configuration

The framework look in multiple directories for its configuration files.

  • /usr/local/etc/dbispipeline.ini used for system wide default.
  • $HOME/.config/dbispipeline.ini used for user specific configurations.
  • ./dbispipeline.ini for project specific configurations.

And example configuration file looks like this:

[database]

# url to your postgres database
host = your.personal.database

# your database user name
user = user

# port of your postgres database, default = 5432
# port = 5432

# password of your database user
password = <secure-password>

# database to use
database = pipelineresults

# table to be used
result_table = my_super_awesome_results

[project]
# this will be stored in the database
name = dbispipeline-test

# this is used to store backups of the execution
# it is possible to override this by setting the DBISPIPELINE_BACKUP_DIR
# environment variable
# the default is the temp dir of the os if this option is not set.
backup_dir = tmp

# this is used to linke the used datasets spcified in data/links.yaml
# it is possible to override this by setting the DBISPIPELINE_DATASET_DIR
# environment variable
dataset_dir = /storage/nas/datasets

[mail]
# email address to use as sender
sender = botname@yourserver.com

# recipient. This should probably be set on a home-directory-basis.
recipient = you@yourserver.com

# smtp server address to use
smtp_server = smtp.yourserver.com

# use smtp authentication, default = no
# authenticate = no

# username for smtp authentication, required if authenticate = yes
# username = foo

# password for smtp authentication, required if authenticate = yes
# password = bar

# port to use for smtp server connection, default = 465
# port = 465

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

dbispipeline-0.8.29.tar.gz (36.8 kB view details)

Uploaded Source

Built Distribution

dbispipeline-0.8.29-py3-none-any.whl (43.4 kB view details)

Uploaded Python 3

File details

Details for the file dbispipeline-0.8.29.tar.gz.

File metadata

  • Download URL: dbispipeline-0.8.29.tar.gz
  • Upload date:
  • Size: 36.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.5

File hashes

Hashes for dbispipeline-0.8.29.tar.gz
Algorithm Hash digest
SHA256 0e6bdcc9831e900188f835205acc1c6a1cd8087bab409ffd6176afa44861c62f
MD5 e54932a563950edfd9f604302951a4c6
BLAKE2b-256 6b2b8404c07f5f6d64ed53c83828fa005d8c525492f8ba3a8b446a9b4cda87ef

See more details on using hashes here.

File details

Details for the file dbispipeline-0.8.29-py3-none-any.whl.

File metadata

  • Download URL: dbispipeline-0.8.29-py3-none-any.whl
  • Upload date:
  • Size: 43.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.5

File hashes

Hashes for dbispipeline-0.8.29-py3-none-any.whl
Algorithm Hash digest
SHA256 83e5c4b928486bb308123c6318a2d6d3cfdf88f7bfcdc71dea61b32fcdbb2126
MD5 4645f938bff29119383c242708f307b8
BLAKE2b-256 0da62f91f674b5cc39bad2f893dc16070043312da93940604789070961e98e52

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page