(NOTE: This is a fork of py4design with the intent of porting it to Python 3 and fixing some of the bugs)
#========================================================
Py4design previously known as Pyliburo
#========================================================
The citation if you are using the library for your research work:
Chen, Kian Wee, and Leslie Norford. 2017. “Developing an Open Python Library for Urban Design Optimisation - Pyliburo.” In Building Simulation 2017, 486–493. San Francisco, USA.
Publications that have used Py4design:
Chen, Kian Wee, and Leslie Norford. 2017. “Evaluating Urban Forms for Comparison Studies in the Massing Design Stage.” Sustainability 9 (6). doi:10.3390/su9060987.
Chen, Kian Wee, Patrick Janssen, and Leslie Norford. 2017. “Automatic Parameterisation of Semantic 3D City Models for Urban Design Optimisation.” In Future Trajectories of Computation in Design – Proceedings of the 17th International Conference on Computer Aided Architectural Design Futures, 51–65. Istanbul, Turkey.
Chen, Kian Wee, Patrick Janssen, and Leslie Norford. 2017. “Automatic Generation of Semantic 3D City Models from Conceptual Massing Models.” In Future Trajectories of Computation in Design – Proceedings of the 17th International Conference on Computer Aided Architectural Design Futures, 84–100. Istanbul, Turkey.
Chen, Kian Wee, and Leslie K Norford. 2016. “Workflow for Generating 3D Urban Models from Open City Data for Performance-Based Urban Design.” In Asim 2016 IBPSA Asia Conference. Jeju, Korea.
API documentation available at http://chenkianwee.github.io/py4design/
Working examples are available at https://github.com/chenkianwee/py4design_examples
The best way to install the library is through conda:
1.) install miniconda/anaconda for python3
(instructions on how to use anaconda: http://conda.pydata.org/docs/using/envs.html)
2.) conda install -c dlr-sc -c algo4bex py4design
3.) conda install spyder (for editing the scripts)
4.) (Optional) install Daysim for running solar simulation from http://daysim.ning.com/ for the daylighting analysis
a.) if c:/daysim/radiance/bin on env path, delete it
#========================================================
list of libraries used in py4design
#========================================================
1.) lxml ((BSD) libxml2 and libxslt2 (MIT))
2.) pyshp (mit license)
3.) pythonocc (GNU LGPL3)
4.) numpy (BSD 3-clause "New" or "Revised" License)
5.) scipy (BSD 3-clause "New" or "Revised" License)
6.) sympy (BSD 3-clause "New" or "Revised" License)
7.) pycollada (BSD 3-clause "New" or "Revised" License)
8.) networkx (BSD 3-clause "New" or "Revised" License)
9.) scikit-learn (BSD 3-clause "New" or "Revised" License)
10.) pymf (GNU General Public License (GPL))
11.) cvxopt (GNU General Public License v3.0)
12.) matplotlib (PSF LICENSE)
13.) numpy-stl (BSD License)
14.) gdal (MIT license)
15.) pyproj (osi approved license))
16.) laspy (BSD License (BSD))
Metadata
Release files for py4design-cea 0.32.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 |
|---|---|---|---|---|
| py4design_cea-0.32.1.tar.gz | 216.6 kB | With provenance | Details for py4design_cea-0.32.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py4design_cea-0.32.1-py3-none-any.whl | Python 3 | none | any | Details for py4design_cea-0.32.1-py3-none-any.whl |
Total release size: 462.3 kB
Release files / py4design_cea-0.32.1.tar.gz
| Download URL | py4design_cea-0.32.1.tar.gz |
|---|---|
| Size | 216.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4760ef1559e6419458ff88d10ac0b157060e52229ad096d53829b35ca4c8bd2
|
|
BLAKE2b-256 checksum How to use checksums |
ac7d520ef786cd39e0b64f60087479e87168b8bf66d15bdbaad40f97e27f12e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logRelease files / py4design_cea-0.32.1-py3-none-any.whl
| Download URL | py4design_cea-0.32.1-py3-none-any.whl |
|---|---|
| Size | 245.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af5df6b59cc0863be358463c81b02a664679d3f5bced966d2366fef9de1effd3
|
|
BLAKE2b-256 checksum How to use checksums |
e8c94c62d431bf3a12215b716982a3ea1f208defec604f68450dbcf7463295c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logSecurity for py4design-cea 0.32.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for py4design_cea-0.32.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logA 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.