Backend data analytics platform for MD2K software

mHealth, machine-learning, data-analysis
pip install cerebralcortex-kernel==3.3.16


CerebralCortex Kernel

Cerebral Cortex is the big data cloud companion of mCerebrum designed to support population-scale data analysis, visualization, model development, and intervention design for mobile sensor data.

You can find more information about MD2K software on our software website or the MD2K organization on our MD2K website.

CerebralCortex Kernel is part of our CerebralCortex cloud platform. CerebralCortex Kernel is mainly responsible to store/retrieve mobile sensor data along with it's metadata.


We have renamed following repositories.

  • CerebralCortex-Platform -> CerebralCortex
  • CerebralCortex - > CerebralCortex-Kernel




CerebralCortex-Kernel is a part of CerebralCortex cloud platform. To test the complete cloud platform, please visit CerebralCortex.

CerebralCortex-Kernel requires minimum Python3.6. To install CerebralCortex-Kernel as an API:

pip3 install cerebralcortex-kernel

  • Note: please use appropriate pip (e.g., pip, pip3, pip3.6 etc.) installed on your machine


  • Python3.6

    • Note: Python3.7 is not compatible with some of the requirements
    • Make sure pip version matches Python version


1 - Do I need whole CerebralCortex cloud platform to use CerebralCortex-Kernal?

No! If you want to use CerebralCortex-Kernel independently then you would need:

2 - How can I change NoSQL storage backend?

CerebralCortex-Kernel follows component based structure. This makes it easier to add/remove features.

3 - How can I replace MySQL with another SQL storage system?

4 - Where are all the backend storage related classes/methods?

In Data manager-Raw. You can add/change any backend storage.


Please read our Contributing Guidelines for details on the process for submitting pull requests to us.

We use the Python PEP 8 Style Guide.

Our Code of Conduct is the Contributor Covenant.

Bug reports can be submitted through JIRA.

Our discussion forum can be found here.


We use Semantic Versioning for versioning the software which is based on the following guidelines.

MAJOR.MINOR.PATCH (example: 3.0.12)

  1. MAJOR version when incompatible API changes are made,
  2. MINOR version when functionality is added in a backwards-compatible manner, and
  3. PATCH version when backwards-compatible bug fixes are introduced.

For the versions available, see this repository's tags.


Link to the list of contributors who participated in this project.


This project is licensed under the BSD 2-Clause - see the license file for details.