Cim2BusBranch
Tansforms PyCIM CIM topologies to a generic bus/branch model that can be used to perform load flow analyses with PYPOWER.
Requirements
Cim2BusBranch runs on Python >= 2.6 and requires PyCIM. PYPOWER is not mandatory but maybe sensible to also be installed.
Installation
You can install Cim2BusBranch easily via PIP (or easy_install):
$ pip install cim2busbranch $ # or: $ easy_install cim2busbranch
You can also download and install Cim2BusBranch manually:
$ cd where/you/put/cim2busbranch/ $ python setup.py install
Cim2BusBranch
The Documentation can be found in the docs/ directory or online.
Metadata
Release files for Cim2BusBranch 0.1
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 |
|---|---|---|---|---|
| Cim2BusBranch-0.1.tar.gz | 280.6 kB | Without provenance | Details for Cim2BusBranch-0.1.tar.gz |
Release files / Cim2BusBranch-0.1.tar.gz
| Download URL | Cim2BusBranch-0.1.tar.gz |
|---|---|
| Size | 280.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02bd8530014d9c9e760e9bd9584a89f92248aed82ab5317104583419ea1c166f
|
|
BLAKE2b-256 checksum How to use checksums |
ad53f93a8a83ccb1f14b5062b91ed50cb52a96d6d6f1b1db5e839fc3c2b244d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Cim2BusBranch 0.1
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.