COMPAS FEA
Finite Element Analysis for COMPAS.
Finite element analysis is a numerical approach to solving a variety of problems in the sciences, mathematics and engineering fields. A continuum such as a fluid or solid volume, is discretised into a set of smaller discrete elements. For each element, data of interest, such as stresses, displacements, temperatures and so on, are found at the nodes and element integration points. The greater the number of elements used to represent the continuum, the better the numerical model will represent the original continuous solution.
The compas_fea package of the compas framework seeks to aid the user, be they an architect, scientist or engineer, in creating and analysing a suitable finite element model for their problem. This is done by creating a Structure object, to contain geometric information about the model, and then to apply loads, displacements, materials and so forth for a subsequent analysis. This construction of the Structure object may be performed in a pure scripting manner with Python, and/or through various modules that help construct the object through present or parametrically generated geometry.
Once the model has been constructed, it may be analysed through a finite element solver in the background, with the data then stored back into the original object or as raw data files. The data can then be post-processed to display the results either through standard compas viewers and applications, or with visualisation support from specific CAD or finite element software.
By using the compas_fea package, the majority of the repetitive scripting tasks needed to perform a geometrically or structurally complex analysis are eliminated, allowing for the rapid investigation of models, with easy to use and streamlined data post-processing and visualisation support.
Installation
First Steps
Questions and Feedback
Issue Tracker
License
Credits
Metadata
Release files for compas-fea 0.3.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 | |
|---|---|---|---|---|
| compas_fea-0.3.3.tar.gz | 80.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compas_fea-0.3.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 184.2 kB
Release files / compas_fea-0.3.3.tar.gz
| Download URL | compas_fea-0.3.3.tar.gz |
|---|---|
| Size | 80.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c0d3c3fecc67b3e48f5a5026a34373a1c155f900f33464e2f2b08ef64f0e1d1
|
|
BLAKE2b-256 checksum How to use checksums |
4fd840d70fac676cb1b21ebf2965bbb631e5ee6471e36df92f3f674f09e63452
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.0 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Release files / compas_fea-0.3.3-py2.py3-none-any.whl
| Download URL | compas_fea-0.3.3-py2.py3-none-any.whl |
|---|---|
| Size | 104.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e58d4601a6c28e4d585fcc88e70c83663d3d893c7458c485dc43ed4a4e349ee7
|
|
BLAKE2b-256 checksum How to use checksums |
c06b329d3069e541fd3bf9ba57f002e9bc7d361ef84387be705ac8264ea076c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.0 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Security for compas-fea 0.3.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.