https://github.com/compas-dev/compas_fea2
Finite Element Analysis toolbox for the COMPAS framework.
https://github.com/compas-dev/compas_fea2
abaqus ansys blender compas fea opensees rhino structures
Last synced: 5 months ago
JSON representation
Finite Element Analysis toolbox for the COMPAS framework.
- Host: GitHub
- URL: https://github.com/compas-dev/compas_fea2
- Owner: compas-dev
- License: mit
- Created: 2020-03-03T11:49:30.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2024-07-29T16:33:05.000Z (9 months ago)
- Last Synced: 2024-09-18T01:38:08.325Z (7 months ago)
- Topics: abaqus, ansys, blender, compas, fea, opensees, rhino, structures
- Language: Python
- Homepage: https://compas.dev/compas_fea2
- Size: 147 MB
- Stars: 6
- Watchers: 7
- Forks: 6
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
- Citation: CITATION.cff
- Authors: AUTHORS.md
Awesome Lists containing this project
README
# compas_fea2
2nd generation of compas_fea. Current Main changes:
* Imporoved API for in-parallel development
* Added User Material subroutines in Abaqus
* Added Parts, Instances and Assembly to Abaqus
## Package objectives
This package aims to create a bridge between the generation of structural geometries and thei analysis
using popular commercial FEA software. The geometry generation features of these software is usually
limited, teduious and time-consuming.
### Users
* simplify finite element analysis with 'pre-made' recipes to help unexperienced users to get meaningful results
* better link with compas and its ecosystem
* unified (as much as possible) approach across multiple backends to help researchers to communicate with their industrial partners. (for example, a researcher develops a structural system for a pavilion using Abaqus, but the enginner of record uses sofistiks to check the results: the analysis model for both structures can be derived from the same script with few changes)
* increase the number of backend solvers supported
### Developers
* clearly separate frontend (geometry generation, problem definition and result displaying) and backend (fea analysis, result post-process) to enhance in-parallel development
* offer frontend and backend developers a framework to help the structuring of their modules and avoid code repetion