Then within the decomposeParDict file, you need to use the

singleProcessorFaceSets

constraint

Can't you achieve the same with a constraint on the AMI patches rather than having to make a faceSet? Or is there a benefit using ``singleProcessorFaceSets`` instead?

How?

there used to be a ``preservePatches`` alongside the ``singleProcessorFaceSets``

No. That's misleading, unfortunately

which have been replaced by another syntax to define constraints

That doesn't do what you think it does

what does it do?

Check this: https://www.openfoam.com/news/main-news/openfoam-v2112/parallel#decomposition

(sorry for hijacking your question Zino! 😅 )

Check the figures

and this

preservePatches (what a misleading name) presevers owner/neifgbour for each cell only

not the entire patches

Alright, got it, but I don't understand the point. I mean I thought the whole idea was to keep AMI interfaces on the same processor, But what happens on your figure once your mesh starts moving? Doesn't it ruin the whole idea of synchronizing owner/neighbors?

in the figure: the cells on the left/right of the green line have the same color, i.e. belong to the same processor

I don't know, but the post I linked above, addresses the same question

Yep, your link on the release notes is pretty clear. It indeed does not do what I thought.

I just don't get the point of synchronizing owner/neighbors cells on a mesh which will move during the simulation, most of the time.

Good to know though, thanks for pointing it out. I'll try to remember it next time I need to use AMI

I think I did try to run it on a reconstructed case and it had the same error, but I'll have to check tomorrow

Hello folks. I'm running a simpleFoam simulation with scalarTransport. I have a fixedValue for my scalar on the walls and I would like to compute the wall flux. Something like ``wallFlux=D*snGrad(s)`` Do you see any flaw/mistake here and how to achieve it? I'm thinking of using a coded function object as I don't see how to do it using others FO

There is a flux FO, https://www.openfoam.com/documentation/guides/latest/doc/guide-fos-field-flux.html#:~:text=Further%20information-,Description,of%20an%20input%20vector%20field. —But I think coded seems straightforward (and easier)!

Thanks, I somehow missed this one! I'm going to give it a try.

I'm using a ``surfaces`` function object to sample data on a surface. Do you guys know if there is an option to output the magnitude of a vector rather than the components? I can't find anything about it but i feel like it's difficult to find stuff in the sampling lib

surfaces
{
    type            surfaces;
    libs            ("libsampling.so");
    writeControl    writeTime;
    surfaceFormat   raw;
    writeFormat     binary;
    fields          (static(p)_coeff wallShearStress);
    interpolationScheme cellPoint;

    surfaces
    (
        aerofoil
        {
            type            patch;
            patches         (aerofoil);
            interpolate     true;
        }
    );
}

You need to calculate mag as a field first, then you can save it in surfaces

I hoped there would be a direct way but I'll survive 😄