From 3bcde9b8e7a2b8d56073d0914e59eec07a0fb89f Mon Sep 17 00:00:00 2001 From: franiqui <101394939+franiqui@users.noreply.github.com> Date: Wed, 29 Oct 2025 13:42:05 +0100 Subject: [PATCH 1/3] Update configuration-mapping.md Addition of feature "spread-profile" in axial-geometric-multiscale mapping. --- content/docs/configuration/basics/configuration-mapping.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/configuration/basics/configuration-mapping.md b/content/docs/configuration/basics/configuration-mapping.md index 9f8cc43f35..aa624fdb29 100644 --- a/content/docs/configuration/basics/configuration-mapping.md +++ b/content/docs/configuration/basics/configuration-mapping.md @@ -177,7 +177,7 @@ The concept also extends to 1D-2D, 2D-3D, and further setups, which are not curr Potential configurations for the axial and radial geometric multiscale mapping look as follows: ```xml - + ``` ```xml @@ -185,9 +185,9 @@ Potential configurations for the axial and radial geometric multiscale mapping l ``` The `multiscale-type` which can be either `"spread"` or `"collect"` refers to whether the participant spreads data from one mesh node to multiple nodes or collects data from multiple mesh nodes into one node. The `multiscale-axis` is the main axis, along which the coupling takes place, i.e. the principal axis of the 1D and 3D participants. The `multiscale-radius` refers to the radius of the circular interface boundary surface. +When using a `"spread"` mapping, the 1D quantity is distributed over the 3D interface using the `spread profile`, which defines how the value varies radially across the circular interface. It can either be "uniform", where the same value is applied to all interface vertices; or "parabolic", in which a parabolic profile is applied (maximum at the centerline, decreasing to zero at the wall). -Since the 1D participant likely computes average quantities, e.g., the average pressure and velocity in a pipe, a velocity profile has to be assumed in order to convert data between the 1D and 3D participant for the axial mapping. Currently, a laminar flow profile is imposed by default, but different profiles might be supported in the future. - +Since the 1D participant likely computes average quantities, e.g., the average pressure and velocity in a pipe, a velocity profile has to be assumed in order to convert data between the 1D and 3D participant for the axial mapping. By default, a laminar flow profile is imposed, but this can be explicitly controlled via the `spread-profile` attribute in the configuration. ## Restrictions for parallel participants As stated above, for parallel participants only `read`-`consistent` and `write`-`conservative` are valid combinations. If want to find out why, have a look at [Benjamin's thesis](https://mediatum.ub.tum.de/doc/1320661/document.pdf), page 85. But what to do if you want a `write`-`consistent` mapping? The trick is to move the mapping to the other participant, then `write` becomes `read`: From d2864e861897429a4fe0587cb7e85b79121e5978 Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Mon, 3 Nov 2025 13:21:45 +0100 Subject: [PATCH 2/3] Update content/docs/configuration/basics/configuration-mapping.md --- content/docs/configuration/basics/configuration-mapping.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/configuration/basics/configuration-mapping.md b/content/docs/configuration/basics/configuration-mapping.md index aa624fdb29..69fe3b7b0a 100644 --- a/content/docs/configuration/basics/configuration-mapping.md +++ b/content/docs/configuration/basics/configuration-mapping.md @@ -185,7 +185,7 @@ Potential configurations for the axial and radial geometric multiscale mapping l ``` The `multiscale-type` which can be either `"spread"` or `"collect"` refers to whether the participant spreads data from one mesh node to multiple nodes or collects data from multiple mesh nodes into one node. The `multiscale-axis` is the main axis, along which the coupling takes place, i.e. the principal axis of the 1D and 3D participants. The `multiscale-radius` refers to the radius of the circular interface boundary surface. -When using a `"spread"` mapping, the 1D quantity is distributed over the 3D interface using the `spread profile`, which defines how the value varies radially across the circular interface. It can either be "uniform", where the same value is applied to all interface vertices; or "parabolic", in which a parabolic profile is applied (maximum at the centerline, decreasing to zero at the wall). +When using a `"spread"` mapping, the 1D quantity is distributed over the 3D interface using the `spread-profile`, which defines how the value varies radially across the circular interface. It can either be `"uniform"`, where the same value is applied to all interface vertices; or `"parabolic"`, in which a parabolic profile is applied (maximum at the centerline, decreasing to zero at the wall). Since the 1D participant likely computes average quantities, e.g., the average pressure and velocity in a pipe, a velocity profile has to be assumed in order to convert data between the 1D and 3D participant for the axial mapping. By default, a laminar flow profile is imposed, but this can be explicitly controlled via the `spread-profile` attribute in the configuration. ## Restrictions for parallel participants From 4af0ab6beb8830fb7d84beb7a5b9920c5c3e9b7f Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Mon, 3 Nov 2025 13:21:52 +0100 Subject: [PATCH 3/3] Update content/docs/configuration/basics/configuration-mapping.md --- content/docs/configuration/basics/configuration-mapping.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/configuration/basics/configuration-mapping.md b/content/docs/configuration/basics/configuration-mapping.md index 69fe3b7b0a..c398421a62 100644 --- a/content/docs/configuration/basics/configuration-mapping.md +++ b/content/docs/configuration/basics/configuration-mapping.md @@ -188,6 +188,7 @@ The `multiscale-type` which can be either `"spread"` or `"collect"` refers to wh When using a `"spread"` mapping, the 1D quantity is distributed over the 3D interface using the `spread-profile`, which defines how the value varies radially across the circular interface. It can either be `"uniform"`, where the same value is applied to all interface vertices; or `"parabolic"`, in which a parabolic profile is applied (maximum at the centerline, decreasing to zero at the wall). Since the 1D participant likely computes average quantities, e.g., the average pressure and velocity in a pipe, a velocity profile has to be assumed in order to convert data between the 1D and 3D participant for the axial mapping. By default, a laminar flow profile is imposed, but this can be explicitly controlled via the `spread-profile` attribute in the configuration. + ## Restrictions for parallel participants As stated above, for parallel participants only `read`-`consistent` and `write`-`conservative` are valid combinations. If want to find out why, have a look at [Benjamin's thesis](https://mediatum.ub.tum.de/doc/1320661/document.pdf), page 85. But what to do if you want a `write`-`consistent` mapping? The trick is to move the mapping to the other participant, then `write` becomes `read`: