AirflowNetwork
Table of Contents
About
This is a small library of functions and classes to examine EnergyPlus AirflowNetwork models. A driver program is provided to analyze models in the epJSON format. To summarize the model contents:
airflownetwork summarize my_model.epJSON
To create a graph of the model in the DOT format:
airflownetwork graph my_model.epJSON
To generate an audit of the model:
airflownetwork audit my_model.epJSON
Further help is available on the command line:
airflownetwork --help
Installation
pip install airflownetwork
Checks
The script checks for a number of issues that may cause an AirflowNetwork to function poorly. These include:
Link Counts
Models with a large number of links (particularly those with too many links between adjacent zones) may model the building correctly and the simulation results may be correct, but the model performance may be quite poor. A situation that has been observed in user models is the use of individual window elements to model each and every window in a buildings. This may be correct, but as the number of windows increases the performance of the model will suffer, and the performance hit may be avoidable if windows the beahve the same are lumped together. For example, if 10 windows connect a zone to the ambient, but all 10 windows experience the same wind pressure and temperature difference, a single winwdow that represents all 10 will be sufficient and eliminate 9 of the 10 calculations required.
The audit command counts the links between zones and flags those that are considered excessive.
Connectedness
Models in which there are zones that are "isolated" (i.e., are not connected to the rest of the model via linkages) have been known to be sensitive to convergence issues. For the most part, the solution procedure can handle multiple isolated subnetworks in a single matrix solution, issues that are encountered with these models can be hard to diagnose. The easiest fix to connect together subnetworks is to add one or more linkages very high flow resistance (e.g., a crack element with a very small flow coefficient).
The audit command checks that the multizone network (just with surfaces) and the full network (multizone + dsitribution) are fully connected. Models with intrazone features are not currently supported.
License
airflownetwork is distributed under the terms of the BSD-3-Clause license.
Metadata
Release files for airflownetwork 1.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 | |
|---|---|---|---|---|
| airflownetwork-1.0.1.tar.gz | 41.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| airflownetwork-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.4 kB
Release files / airflownetwork-1.0.1.tar.gz
| Download URL | airflownetwork-1.0.1.tar.gz |
|---|---|
| Size | 41.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73505b644e521d9e54ac62b201813cb3e3057e74f3a6f236ccece6d26388d7f5
|
|
BLAKE2b-256 checksum How to use checksums |
6834603c09f831c8def523915d4e2826f31d7f5801b905f1015e86ee763e671b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / airflownetwork-1.0.1-py3-none-any.whl
| Download URL | airflownetwork-1.0.1-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16146dd7efac654dbaac98c955ce865e9ba9ba66e9c6d4eb29781967e874fd24
|
|
BLAKE2b-256 checksum How to use checksums |
8ebc08cf7258782a7b6c76c8f3aba8ed2e77a2dc39b00722335b42e0c4ed7901
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for airflownetwork 1.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.