... | ... | @@ -118,12 +118,16 @@ Currently, the post processing (i.e. the visualization of the superposition of t |
|
|
|
|
|
---
|
|
|
|
|
|
### Interactive Plotting Tool
|
|
|
### 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).
|
|
|
|
|
|
The aim of this project is to add the support for binary output to all the missing entities. A vast library of examples can be obtained simply looking at the current implementation for the supported entities.
|
|
|
|
|
|
**Category**: [Post-process](#post-process)\
|
|
|
**Programming Languages**: Python\
|
|
|
**Keywords**: UI, post-process\
|
|
|
**Difficulty**: Low/Intermediate\
|
|
|
**Programming Languages**: C++\
|
|
|
**Keywords**: post-process, NetCDF\
|
|
|
**Difficulty**: Low\
|
|
|
**Mentors**: Andrea Zanoni\
|
|
|
|
|
|
---
|
... | ... | @@ -146,7 +150,14 @@ The desired output is the implementation of a new `zeromq` `socket type` for the |
|
|
|
|
|
### MBDyn-DUST Module
|
|
|
|
|
|
**TODO**
|
|
|
MBDyn can be coupled with external software, allowing it to be inserted into co-simulation pipelines. The most common application is Fluid-Structure Interaction (FSI), which is the field for which MBDyn was initially developed.
|
|
|
|
|
|
[DUST](https://public.gitlab.polimi.it/DAER/dust) is a mid-fidelity aerodynamic solver, designed to provide fast estimated good enough for aircraft conceptual design. It is based on an
|
|
|
integral boundary element formulation of the aerodynamic problem and vortex-particle modelling of the wakes.
|
|
|
|
|
|
MBDyn is currently typically coupled with DUST using [preCICE](https://precice.org/). However, for most applications, this is a rather unnecessary complication, since all is requested from [preCICE](https://precice.org/) is to make the two software exchange data at each timestep and give each other the OK to go to to the next step at convergence.
|
|
|
|
|
|
This project aims at developing an *in-house* solution for the coupling, in the form of a MBDyn [module](https://public.gitlab.polimi.it/DAER/mbdyn/-/wikis/home#what-are-run-time-loadable-modules-and-how-do-they-work). It will follow a similar pattern as the one from the 2020 GSoC edition from [Runsen Zhang](https://public.gitlab.polimi.it/DAER/mbdyn/-/wikis/GSoC-Students-Blogs#a-user-defined-runtime-loadable-module-template-for-co-simulation-with-chronoengine), who created a template module for the co-simulation of MBDyn and [Chrono](https://projectchrono.org/).
|
|
|
|
|
|
**Category**: [Modeling Capabilities](#modeling-capabilities)\
|
|
|
**Programming Languages**: C/C++\
|
... | ... | |