# Map 2D axisymmetric to 3D

**URL:** <https://precice.discourse.group/t/map-2d-axisymmetric-to-3d/2997>\
**Category:** Using preCICE\
**Tags:** data-mapping\
**Created:** [August 18, 2026, 3:44pm UTC](https://precice.discourse.group/t/map-2d-axisymmetric-to-3d/2997 "2026-08-18T15:44:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![exkroy](https://avatars.discourse-cdn.com/v4/letter/e/f04885/32.png) [@exkroy](https://precice.discourse.group/u/exkroy)\
**Post date:** [August 18, 2026, 3:44pm UTC](https://precice.discourse.group/t/map-2d-axisymmetric-to-3d/2997/1 "2026-08-18T15:44:58Z")

</div>

Hello,

my setup is as follows:

 ![grafik](https://global.discourse-cdn.com/free1/uploads/precice/original/2X/c/c0d8b71931bafc1526cdb60fe21e0635c95e1ef8.png)

Both simulations are currently 2D axisymmetric (OpenFOAM and solids4foam respectively). Temperatures and heat transfer coefficients are exchanged. Now I would like to simulate the solid not with a wedge, but as a half-symmetric model (or, if necessary, as a full model). However, due to the expected computation times, it is not possible to adapt the fluid model accordingly either.

Would it be possible to do this using 2D-3D [geometric multiscale mapping](https://precice.org/configuration-mapping.html#geometric-multiscale-mapping)? In other words, mapping between the fluid-wedge and solid-symmetry meshes? Unfortunately, I can’t quite make sense of the explanation on the website.

Many thanks for your fantastic work!

EDIT:  
The way I imagine it, it would look something like this:

 ![grafik](https://global.discourse-cdn.com/free1/uploads/precice/original/2X/7/74308a7c32140b25259742d46a05978795a749e0.jpeg)

---

<div class="post-metadata">

**Author:** ![Makis](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/makis/32/25_2.png) [@Makis](https://precice.discourse.group/u/Makis)\
**Post date:** [August 21, 2026, 12:51pm UTC](https://precice.discourse.group/t/map-2d-axisymmetric-to-3d/2997/2 "2026-08-21T12:51:24Z")

</div>

Hi @exkroy,

I see that you want to save resources by modeling the fluid with a wedge mesh, but the coupling to a full solid mesh cannot be done with the geometric multiscale mapping.

The “radial mapping” is only provided for 1D-2D or 1D-3D mapping at the moment, and is meant for two domains embedded in each other.

For what you want to do, I would suggest an intermediate step to convert from the wedge to a full step. You can implement that either via a Python Action, or on one of your adapters.

Still, I wonder: when coupling a symmetric to a non-symmetric domain, how should the non-symmetric effects be mapped to the symmetric domain? One would need to make assumptions there (e.g., averaging), and you would best make these one of your adapters.

---

<div class="post-metadata">

**Author:** ![exkroy](https://avatars.discourse-cdn.com/v4/letter/e/f04885/32.png) [@exkroy](https://precice.discourse.group/u/exkroy)\
**Post date:** [August 24, 2026, 10:21am UTC](https://precice.discourse.group/t/map-2d-axisymmetric-to-3d/2997/3 "2026-08-24T10:21:12Z")

</div>

Hi Makis,

Thank you for your suggested solutions!

I can see from the documentation that the Python Actions offer two options for `timing`: `write-mapping-post` and `read-mapping-post`. But aren’t both of these already too late for initialising the mapping?

> [@Makis](#):
>
> Still, I wonder: when coupling a symmetric to a non-symmetric domain, how should the non-symmetric effects be mapped to the symmetric domain? One would need to make assumptions there (e.g., averaging), and you would best make these one of your adapters.

That’s a good point. To be honest, I hadn’t really thought about that before. The non-symmetrical effects relate to the deformation of the solid. The impact on the temperature should be negligible. At the moment, I’m only exchanging temperatures and heat transfer coefficients.