SPATIAL AND TEMPORAL CORRELATION ANALYSIS WITH APPLICATION TO FMRI Data
Correlation analysis between two groups of time series is common in many fields, for example in analysis of functional magnetic resonance imaging (fMRI) data. The most widely used approach in fMRI is probably to compute Pearson's correlation between the group-mean temporal vectors, averaged across the (spatial) variables in each group. This approach does not account for the continuity of the time series and the inhomogeneity in the variables. In this project, we propose a spatial and temporal correlation analysis (STC) that addresses these two issues simultaneously. It integrates the functional correlation and canonical correlation analysis (CCA) in a unified optimization-based framework. This allows, for example, varying contributions of spatial variables and increased signal strength. Simulation results show the proposed method outperforms other competing methods. Applying to a fMRI dataset, we identify the connection strength between brain regions and the inhomogeneous functions within regions.
Getting Started
Prerequisites
What things you need to install the software and how to install them
See setup.py for details of packages requirements.
Installing from GitHub
Download the packages by using git clone https://github.com/xuefeicao/stc.git
python setup.py install
If you experience problems related to installing the dependency Matplotlib on OSX, please see https://matplotlib.org/faq/osx_framework.html
Running the tests
Go to test folder, run
python test.py
|## Built With
- Python 2.7
Compatibility
- Python 2.7 (Guaranteed)
Authors
- Jun Ke
- Xuefei Cao - Maintainer - (https://github.com/xuefeicao)
- Xi Luo (http://bigcomplexdata.com/)
License
This project is licensed under the MIT License - see the LICENSE file for details
Metadata
Release files for stcorr 0.0.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 | |
|---|---|---|---|---|
| stcorr-0.0.0.tar.gz | 4.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stcorr-0.0.0-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 10.1 kB
Release files / stcorr-0.0.0.tar.gz
| Download URL | stcorr-0.0.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
173fa594047ed5cf3970dac0221cdb873d6fbb53ae20d7c0e2173ac74b4cd741
|
|
BLAKE2b-256 checksum How to use checksums |
2f937c4601db7aa66f093e93adbf817d12877a66d7c027ff1be18669f41be23e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/2.7.15
|
Release files / stcorr-0.0.0-py2-none-any.whl
| Download URL | stcorr-0.0.0-py2-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
8e588f2fec2734592933a27caa3e9352005066b8e34d45dd90877620bb34b494
|
|
BLAKE2b-256 checksum How to use checksums |
e0fc1128d07cda2f4c840f7b89d62c34da4f85c313f847662e7574a371e8499e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/2.7.15
|
Security for stcorr 0.0.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.