nrn-diff
Usage
>>> from nrndiff import nrn_diff
>>> from neuron import h
>>> s1 = h.Section()
>>> s2 = h.Section()
>>> nrn_diff(s1, s2)
[]
>>> s2.L = s1.L * 2
>>> nrn_diff(s1, s2)
[
<nrndiff._differences.SectionLengthDifference object at 0x7f52eb4d3310>,
<nrndiff._differences.SegmentAreaDifference object at 0x7f52eb47de80>,
<nrndiff._differences.SegmentVolumeDifference object at 0x7f52eb47d7c0>,
<nrndiff._differences.SegmentInputResistanceDifference object at 0x7f52eb47df40>
]
Metadata
Release files for nrn-diff 0.0.3
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 | |
|---|---|---|---|---|
| nrn_diff-0.0.3.tar.gz | 4.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nrn_diff-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / nrn_diff-0.0.3.tar.gz
| Download URL | nrn_diff-0.0.3.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d934e8ade6abcf1a2248830dc3f410c11dcb6c62a75d29300037ed4bf94da26c
|
|
BLAKE2b-256 checksum How to use checksums |
4c2d9ede1849d1e286c1811376ae5ef92548f526bd75803ff975d4aaf137f2c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.9
|
Release files / nrn_diff-0.0.3-py3-none-any.whl
| Download URL | nrn_diff-0.0.3-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88c1fe6452f2f2876dd77ce7a81ded712629046e7d85098339ff976d81145715
|
|
BLAKE2b-256 checksum How to use checksums |
8b060f1e2eeea52dfac9cb61e34bcc2f37b4d4e5169938e046c9735fa8258c77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.9
|
Security for nrn-diff 0.0.3
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.