pyccm
This package computes the Convergent Cross Mapping described by Sugihara et al., 2012: “Detecting Causality in Complex Ecosystems”. Science 338: 496–500
This code was adapted from https://github.com/cjbayesian/rccm by Corey Chivers.
Frederic Laliberte, Univerity of Toronto, 2014
The Natural Sciences and Engineering Research Council of Canada (NSERC/CRSNG) funded FBL during this project.
Version History
- 0.4: The correlations are computed on the vector at lag 0. Note: this returns to the Sugihara et al. approach.
Bug fixes with E>2
0.3: The correlations are computed on the lagged vectors. Note: this departs from Sugihara et al.
0.2: Added the capability of analyzing time series limited to a few months per year
0.1: First version
1 maintainer
Metadata
1 maintainer
Release files for pyccm 0.4
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 |
|---|---|---|---|---|
| pyccm-0.4.tar.gz | 5.4 kB | Without provenance | Details for pyccm-0.4.tar.gz |
Release files / pyccm-0.4.tar.gz
| Download URL | pyccm-0.4.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec1a08a62a6f8745bc87f1546e50892bc613f44e0ebae33ef63c4ad5de4fdc18
|
|
BLAKE2b-256 checksum How to use checksums |
9e598ac925de720f7cee84add14e41ef76ed483d058f2a4f034420f7a078146c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyccm 0.4
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.
