zkcurvefit module has curvefit method which takes 3 arguments file-to-read, file-to-write, timestep-max , density_coeff (dilution factor), plot = “on” or “off” reads the file and curvefits every column with the initial column which should be timestep column [1:tmax].
“It’s written for decaying datasets.”
It write 3 files
1 = all curvefit data points 2 = once in 50 curvefit data points 3 = koff values where koff = 1/tauOff
For curvefit to work best you need to have big datasets with first column is timestep with 1 increments starting with 1 since timestep 0 disrupts the curveffitting algorithm used here.
1 maintainer
Metadata
1 maintainer
Release files for zkcurvefit 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zkcurvefit-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for zkcurvefit-0.1.4-py3-none-any.whl |
Release files / zkcurvefit-0.1.4-py3-none-any.whl
| Download URL | zkcurvefit-0.1.4-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6715308b5498649d263a36560afd7d16c440bddb01b950516b41068999d9ac02
|
|
BLAKE2b-256 checksum How to use checksums |
3aa58229a6bd827776eee71e85f7b7e751bdc175c2e5f0bf771b97bda7362a52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.9.1
|
Security for zkcurvefit 0.1.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.
