... | ... | @@ -19,7 +19,6 @@ Furthermore, for the 2024 GSoC edition we completely re-structured the project p |
|
|
|
|
|
- **Post-process**
|
|
|
- [Blendyn Development](#blendyn-development)
|
|
|
- [Modal element visualization](#modal-element-visualization)
|
|
|
- [Interactive plotting tool](#interactive-plotting-tool)
|
|
|
|
|
|
- **IPC/RT**
|
... | ... | @@ -90,7 +89,6 @@ It is simple to use and generates 3D animations that represent the exact model m |
|
|
- only fixed timestep simulation output is currently supported, variable timestep should be allowed also
|
|
|
- support the live plotting of MBDyn signals, for example leveraging the NetCDF output `sync` feature
|
|
|
- support the plotting of signals derived from arbitrary compositions of MBDyn signals (e.g. the sum of two signals)
|
|
|
- support for the visualization of modal elements should be introduced (see the next project)
|
|
|
|
|
|
The last point is the one requiring the largest effort, which is why it has been extrapolated to a [standalone project](#modal-element-visualization). This is to highlight the flexibility we have with the projects: this aspect can be part of a large (350 hours) project, or it can be a standalone mid-sized (175 hours) project.
|
|
|
|
... | ... | @@ -103,21 +101,6 @@ The last point is the one requiring the largest effort, which is why it has been |
|
|
|
|
|
---
|
|
|
|
|
|
### Modal element visualization
|
|
|
|
|
|
MBDyn's modal joint implements a Component Mode Synthesis (CMS) deformable body. The CMS element interacts with the multibody model only in specific nodes (interface nodes). The full dynamics of the body is condensed into the superposition of the responses of its modes of vibrations, that it outputs in the form of the time histories of its modal coordinates, together with the rigid body motion of a specific node used to define the floating reference frame, the modal node.
|
|
|
|
|
|
Currently, the post processing (i.e. the visualization of the superposition of the rigid and the deformative motion of the body) for the element is not implemented in any of the existing post-processing tools. The project aims at filling this gap, by adding support for the flexible superelement to [Blendyn](https://github.com/zanoni-mbdyn/blendyn).
|
|
|
|
|
|
**Category**: [User Interface](#user-interface)\
|
|
|
**Programming Languages**: Python\
|
|
|
**Keywords**: Blender, UI, post-process\
|
|
|
**Difficulty**: Intermediate\
|
|
|
**Mentors**: Andrea Zanoni\
|
|
|
**ENTRY TEST**: Complete step 1 of standard MBDyn GSoC [entry test](https://gitlab.polimi.it/Pub/mbdyn/wikis/Google-Summer-of-Code/Entry-Test), visualize the results of your simulation using [Blendyn](https://github.com/zanoni-mbdyn/blendyn), simulate the [ssbeam](https://www.mbdyn.org/userfiles/documents/examples/ssbeam.tar.gz) MBDyn example, visualize the trajectory of at least one of the FEM nodes of the ssbeam beam model, using a software of your choice (e.g. Octave, Scilab, Python, gnuplot, ...): refer to section 8.12.32 of the MBDyn input manual to gather information about the modal element output.
|
|
|
|
|
|
---
|
|
|
|
|
|
### Complete binary output
|
|
|
|
|
|
MBDyn can output simulation results in [NetCDF](https://www.unidata.ucar.edu/software/netcdf/) format, speeding up significantly the manipulation of output data for visualization and processing. Currently, the support for binary output is still not complete among all the MBDyn entitites. For example, drives are currently not supported, nor are numerous user-defined elements contained in [modules](home#what-are-run-time-loadable-modules-and-how-do-they-work).
|
... | ... | |