|
|
|
|
|
|
|
|
|
|
|
The project is structured 6 parts:
|
|
|
|
* Two are the main core of the project: *io* for input/output and *analysis* where main developments are done.
|
|
|
|
* Four are dedicated to support the use of the library: *examples* to apply the developments done in *analysis*, *GUI* for graphical user interface for quick using of the library, *templates* to gather common templates and finally *sandbox* where all developers has a folder to try its project.
|
|
|
|
|
|
|
|
|
|
|
|
<img src=".wiki-images/library-structure.jpg" height="350" class="center">
|
|
|
|
|
|
|
|
|
|
|
|
**analysis** aims to gather all analysis tools such as:
|
|
|
|
|
|
|
|
- *tools.py* : general tools
|
|
|
|
|
|
|
|
- *constitutive_laws.py* : behavior laws and characterization
|
|
|
|
|
|
|
|
- *geometries.py* : geometry reconstruction, smoothing, compute lengths, surfaces, ...
|
|
|
|
|
|
|
|
- *models.py* : mesh scaling, point location, properties assignment
|
|
|
|
|
|
|
|
- *images.py* : tracking tools, image analysis, ...
|
|
|
|
|
|
|
|
**inout** aims to gather input/output functions reading and writing formats
|
|
|
|
|
|
|
|
- *inout.py*
|
|
|
|
|
|
|
|
**templates** aims to gather document templates commonly used by the team, such as templates for reports, articles, presentations or code files.
|
|
|
|
|
|
|
|
**examples** aims to provide simple scripts to test all functions and classes developed.
|
|
|
|
If data are added to run the examples remember to use git LFS. They serve to check the library tools and provide simple guides for applying and integrating the functions and classes developed.
|
|
|
|
|
|
|
|
**GUI** aims to include all programs with a Graphical User Interface, that is, interactive tools accessible to non-programmers.
|
|
|
|
|
|
|
|
**Sandbox** is intended for development of new tools and enhancement of existing tools.
|
|
|
|
|
