2025 FSI Week Meeting Notes

[matekelemen]

Tasks

Versioning (@KratosMultiphysics/technical-committee)

• require an identifier in MDPA that references a specific commit hash
  • discussion: what identifies the version? commit hash? version number
• require a version tag in the JSONs
• embed version hash into the restart file
• embed commit hash into Model?

CoSim

• simplify inheritance structures
• make it clearer when and which InitializeSolutionStep and FinalizeSolutionStep is called
• extend support for other solvers
  • Star-CCM+
  • FLOWer (within WINSENTvalid project - probably restricted access)
  • OpenFOAM (give it more visibility and make sure it stays up to date with current Kratos versions)

Others

• @include_json for materials or leave it as it is right now? @pooyan-dadvand
• coupled sensitivities @sunethwarna @Igarizza @matekelemen
  • check out other projects (e.g.: MDOLab)
• revamped adjoint calculation in standard elements
  • @sunethwarna pitch design when finalized to @RiccardoRossi and @pooyan-dadvand
• push forward the geometry-based I/O and revamp the MeshIO stuff @rubenzorrilla
• push forward new strategies implementation @rubenzorrilla @RiccardoRossi
• populate and promote the use of the FlowGraph @rubenzorrilla @RiccardoRossi @roigcarlo
• populate the registry and leverage its usage as factory @rubenzorrilla @pooyan-dadvand @roigcarlo

Visibility and PR

• organize Kratos hackathon (Barcelona this year, Munich next) - @RiccardoRossi
• higher visibility for machine learning methods in Kratos @KratosMultiphysics/rom
• revamp our landing page @matekelemen
• TUM software lab for linear solvers, 3rd party solvers @matekelemen @sunethwarna

[loumalouomega]

Just one comment and I will comment indepently each point. Now GithHub allows sub issues, and it will be more practical to discuss that indepentdently.

[loumalouomega]

Feel free to open more sib-issues if you consider it relevant.

[loumalouomega]

* Organize Kratos hackathon (Barcelona this year, Munich next) - [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/RiccardoRossi?size=32">@RiccardoRossi](https://github.com/RiccardoRossi)

Can you epand this @RiccardoRossi ?

* revamp our landing page [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/44344022?s=64&amp;u=d041883a1eb92bac9942504475823f0e11ded6af&amp;v=4">@matekelemen](https://github.com/matekelemen)

What page do you mean?

* TUM software lab for linear solvers, 3rd party solvers [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/44344022?s=64&amp;u=d041883a1eb92bac9942504475823f0e11ded6af&amp;v=4">@matekelemen](https://github.com/matekelemen) [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/sunethwarna?size=32">@sunethwarna](https://github.com/sunethwarna)

I am interested on this, what plans do you have exactly?

[matekelemen]

• TUM software lab for linear solvers, 3rd party solvers

I am interested on this, what plans do you have exactly?

Sorry, these are notes I took on the fly and assumed everyone would be familiar with the terms. Software Lab is not actually a lab (in the US sense), but a 9 month long project course at TU Munich (mostly for computational mechanics students) in which they have to work in groups of 3-4 to complete software and modeling related projects from (mostly) the industry and (occasionally) academics.

As for the project, I wanted to try hypre for a very long time (especially BoomerAMG), but I never had the time so this course would be a nice way to kickstart things.

By 3rd party solvers I mean Star-CCM+ for example, or other software that solve domain-specific problems, not linear solvers. This would be a different project.

[matekelemen]

• revamp our landing page

What page do you mean?

I mean our root readme.md. It's been bugging me ever since I joined the project, and I think we could do a better job at it.

• fix the language (I mean English). Specifically typos but I'd also rewrite the sentences to be grammatically correct and feel more native.
• deport information that does not belong on the landing page
  • contributors should go to a separate page dedicated to community and contribution info
  • applications belong on a documentation page that explains Kratos' structure
  • Examples of use should be a mini gallery that redirects to the examples repo
  • ...
• reorder and format the content to make more sense and feel more organized

The reason for professionalizing our landing page is that if we start pushing publicity (e.g.: Riccardo's hackathons or the annual FSI course), the first thing any newcomer will come in contact with is our main readme. I guess I don't have to explain how important first impressions are.