cedalion - fNIRS analysis toolbox
To avoid misinterpretations and to facilitate studies in naturalistic environments, fNIRS measurements will increasingly be combined with recordings from physiological sensors and other neuroimaging modalities. The aim of this toolbox is to facilitate this kind of analyses, i.e. it should allow the easy integration of machine learning techniques and provide unsupervised decomposition techniques for multimodal fNIRS signals.
Documentation
The documentation contains installation instructions as well as several example notebooks that illustrate the functionality of the toolbox. For discussions and help you can visit the cedalion forum on openfnirs.org
Development environment
To create a conda environment with the necessary dependencies run:
$ conda env create -n cedalion -f environment_dev.yml
Afterwards activate the environment and add an editable install of cedalion to it:
$ conda activate cedalion
$ pip install -e .
$ bash install_nirfaster.sh CPU # or GPU
This will also install Jupyter Notebook to run the example notebooks.
If conda is too slow consider using the faster drop-in replacement mamba. If you have Miniconda or Anaconda you can install mamba with: ''' $ conda install mamba -c conda-forge ''' and then create the environment with
$ mamba env create -n cedalion -f environment_dev.yml
Please note: If this does not socceed there is another route to go: Install the libmamba solver ''' $ conda install -n base conda-libmamba-solver ''' and then build the environment with the --solver=libmamba
$ conda env create -n cedalion -f environment_dev.yml --solver=libmamba
How to cite Cedalion
A paper for the toolbox is currently in the making. If you use this toolbox for a publication in the meantime, please cite us using GitHub's "Cite this repository" feature in the "About" section. If you want to contact us or learn more about the IBS-Lab please go to https://www.ibs-lab.com/
Metadata
Release files for cedalion 25.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cedalion-25.1.0.tar.gz | 49.0 MB | Without provenance | Details for cedalion-25.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cedalion-25.1.0-py3-none-any.whl | Python 3 | none | any | Details for cedalion-25.1.0-py3-none-any.whl |
Total release size: 49.3 MB
Release files / cedalion-25.1.0.tar.gz
| Download URL | cedalion-25.1.0.tar.gz |
|---|---|
| Size | 49.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35ef2f798af895347e989532a4965bdaaa984467439a4a3df0d9362bd54c4daf
|
|
BLAKE2b-256 checksum How to use checksums |
4cd044dbe5e3bdea3e80fe48ee07aa125a1b3ef467211a432809e6c8d4fac533
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Release files / cedalion-25.1.0-py3-none-any.whl
| Download URL | cedalion-25.1.0-py3-none-any.whl |
|---|---|
| Size | 348.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7136de0c237756e70e59419c865523bff46653ae1f6b6fbff60a07c5611f6d38
|
|
BLAKE2b-256 checksum How to use checksums |
f2bd0d7b494d6c8aa284d492d64944732a09221f1c92472cc2bf65b26c354000
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Security for cedalion 25.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.