Introduction to the Lossless Pipeline
This EEG processing pipeline is especially useful for the following scenarios:
- You want to keep your EEG data in a continuous state, allowing you the flexibility to epoch your data at a later stage.
- You are part of a research team or community that shares a common dataset, and you want to process the data once in a way that can be used for multiple analyses (i.e., one analysis can segment the cleaned data into 10-second epochs and filter the data betweeen 1-30Hz, while another analysis can use 1-second epochs with no filter, etc.)
- You want to be able to do a hands on review of the pre-processing results for each file.
📘 Installation and usage instructions
The development version can be installed from GitHub with
$ git clone git@github.com:lina-usc/pylossless.git
$ pip install --editable ./pylossless
for an editable installation, or simply with
$ pip install git+https://github.com/lina-usc/pylossless.git
for a static version.
Please find the full documentation at pylossless.readthedocs.io.
▶️ Running the pyLossless Pipeline
Below is a minimal example that runs the pipeline one of MNE's sample files.
import pylossless as ll
import mne
fname = mne.datasets.sample.data_path() / 'MEG' / 'sample' / 'sample_audvis_raw.fif'
raw = mne.io.read_raw_fif(fname, preload=True)
config = ll.config.Config()
config.load_default()
config.save("my_project_ll_config.yaml")
pipeline = ll.LosslessPipeline('my_project_ll_config.yaml')
pipeline.run_with_raw(raw)
Once it is completed, You can see what channels and times were flagged:
print(pipeline.flagged_chs)
print(pipeline.flagged_epochs)
Once you are ready, you can save your file:
pipeline.save(pipeline.get_derivative_path(bids_path), overwrite=True)
👩💻 Dashboard Review
After running the Lossless pipeline, you can launch the Quality Control Review (QC) dashboard to review the pipeline's decisions on each file! You can flag additional channels, times and components, and edit flags made by the pipeline.
First install the dashboard requirements
$ cd ./path/to/pylossless/on/your/computer
$ pip install --editable .[dash]
$ pylossless_qc
▶️ Example HPC Environment Setup
If you are a Canadian researcher working on an HPC system such as Narval:
module load python/3.10
# Build the virtualenv in your homedir
virtualenv --no-download eeg-env
source eeg-env/bin/activate
pip install --no-index mne
pip install --no-index pandas
pip install --no-index xarray
pip install --no-index pyyaml
pip install --no-index sklearn
pip install mne_bids
# Clone down mne-iclabel and switch to the right version and install it locally
git clone https://github.com/mne-tools/mne-icalabel.git
cd mne-icalabel
git checkout maint/0.4
pip install .
# Clone down pipeline and install without reading dependencies
git clone git@github.com:lina-usc/pylossless.git
cd pylossless
pip install --no-deps .
# Verify that the package has installed correct with an import
python -c 'import pylossless'
Metadata
Release files for pylossless 0.2.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 | |
|---|---|---|---|---|
| pylossless-0.2.0.tar.gz | 49.9 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pylossless-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 99.6 MB
Release files / pylossless-0.2.0.tar.gz
| Download URL | pylossless-0.2.0.tar.gz |
|---|---|
| Size | 49.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ecb46aeddc825969fe0450f6c80d5462b2a9e63020219daab7bf27da7f267e3
|
|
BLAKE2b-256 checksum How to use checksums |
e0d44152d207b3776dbce582445deef6b0cb257a7ac6d705eee72c066d4bb5f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2024.
Transparency logRelease files / pylossless-0.2.0-py3-none-any.whl
| Download URL | pylossless-0.2.0-py3-none-any.whl |
|---|---|
| Size | 49.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2452630d114d0f3ecd4b8a3c7b7ed7180fee93f6712e3fcb6b34ae14a5b3d8ac
|
|
BLAKE2b-256 checksum How to use checksums |
264dd4bbc151396c4aed7527e949cdf54aca62d0994ad9947c679543bb832ea0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2024.
Transparency logSecurity for pylossless 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pylossless-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 17, 2024.
Transparency logA 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.