| ... | ... | @@ -44,6 +44,8 @@ In this context, many possibilities for GSoC projects can be devised. A non-comp |
|
|
|
- Addition of classes that handle the generation of rotary-wing aircraft components (like HingelessRotor, FullyArticulatedRotor, Wing, etc...)
|
|
|
|
- Addition of classes to handle flexible element meshing
|
|
|
|
|
|
|
|
This project can be scoped at **175** or **350** hours.
|
|
|
|
|
|
|
|
**Category**: [User Interface](#user-interface)\
|
|
|
|
**Programming Languages**: Python\
|
|
|
|
**Difficulty**: Low/Intermediate\
|
| ... | ... | @@ -150,6 +152,8 @@ MBDyn is currently typically coupled with DUST using [preCICE](https://precice.o |
|
|
|
|
|
|
|
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/).
|
|
|
|
|
|
|
|
This is a **350** hours project.
|
|
|
|
|
|
|
|
**Category**: [Modeling Capabilities](#modeling-capabilities)\
|
|
|
|
**Programming Languages**: C/C++\
|
|
|
|
**Keywords**: Inter-Process Communication, Co-Simulation\
|
| ... | ... | |
