[a.weber]

Hello everyone,

I'm currently working on some changes on the sprayFoam solver to do different breakup and coalescence models.

It would be great to visualize areas of higher breakup/coalescence frequency. Therefore I create scalarfields (e.g. n_bu for breakup and n_coal) just as a counter for each cell. If breakup occurs in a cell, the value should just count up. Later on I could calculate the breakup freqeuncy easily with this field.

Breakup is mainly defined in
...../src/lagrangian/spray/parcels/Templates/SprayParcel/SprayParcel.C

What do I have to add there, to get my counter working?
Since SprayParcel.C is meant to only treat the particles fields, there is no direct access to the mesh fields (in some way read-only through interpolation of velocity Uc_ = td.UInterp().interpolate(....); )

The Idea is really easy, but I was not able to find a solution yet.

Best regards,
Andy

[dkxls]

Originally Posted by a.weber

Therefore I create scalarfields (e.g. n_bu for breakup and n_coal) just as a counter for each cell. If breakup occurs in a cell, the value should just count up.

Why would you want to get the breakup count per cell, why not per parcel?

Well, actually both could be quite interesting.

There is a unused "user" variable in the SprayParcel class. You could use that as a counter. The problem here is just that you determine the breakup event inside the BreakupModel classes, which don't have access to the "user" variable, or the mesh for that matter.

I'm not sure if it works, but you could try to pass the user variable to:

bool Foam::BreakupModel<CloudType>::update

This requires you to also change all breakup models, but that would be my best bet right now.

Originally Posted by a.weber

Since SprayParcel.C is meant to only treat the particles fields, there is no direct access to the mesh fields (in some way read-only through interpolation of velocity Uc_ = td.UInterp().interpolate(....); )

If you really start coding inside the SprayParcel template then you have access to the mesh. Can't remember where the mesh is kept, but I would probably check the KinematicParcel or KinematicCloud class first.
Once you have access to your fields you can also pass them to the breakup models and get your counter per cell.

I just saw that you have access to the cell number and TrackData already inside the void Foam::SprayParcel<ParcelType>::calcBreakup function.
You should get access to the mesh like this (haven't tested it though):

 const polyMesh& mesh = td.cloud().pMesh();

[a.weber]

Why would you want to get the breakup count per cell, why not per parcel?

Using Breakup AND Coalescence Events together would end in a loss of information since one of the coalescing droplets/parcels will be deleted in the process.

[a.weber]

Thank you for the quick reply!

I'm trying to define n_bu trough an IOobject, somehow like this:

const polyMesh& mesh = td.cloud().pMesh();

volScalarField n_bu
(
IOobject
(
"n_bu",
td.cloud().db().time().timeName(),
td.cloud().db(),
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);

But that wont work because I need the fvMesh to create an IOobject (but only have the polyMesh). I hope I've understood that right....

So I think what I have to do is to pass the fvMesh down to SprayParcel.C (e.g. from KinematicCloud.C).

Or is there a easier/faster solution to obtain the fvMesh???

[a.weber]

Still haven't found a solution yet.

You're right so far, i can make use of
td.cloud().pMesh();
in
Foam::SprayParcel<ParcelType>::calcBreakup
but so far I have only managed to get read-only access to the field values (e.g. to my counter-field "n_bu" with lookupObject<volScalarField>("n_bu")).

So is there a way to get write access somehow to that field, probably with a Pointer?