Can someone maybe tell me how to improve my results and tell me if this is somewhat physically correct

I especially want to know if particles in the bottom part are being transported away or not, do I need multiphase for that? Or is this enaugh for an engineering approximation

What am I looking at? The kidneys of a roblox?

I was thinking it was some sort of filling of a container from very small side vents. Or some way of hydrostatic pressure pushing up a fluid

Ah fuck I didn't realize that I haven't described haha. It is a tool vibrating at a specific frequency in a standing fluid. Boundary conditions are just uniform (0 0 0) and zeroGradient on topLeft and topRight to represent farField. It is only moving very small distances so its hard to see.

At least thats what I was trying to do 😄

Was hoping to show that particles are transported away faster out of the bottom part when the tool vibrates

Not multiphase but lagrangian.

You could use something like the icoUncoupledKinematicCloud function object to compute the transport of a particle cloud based on the velocity field computed by your solver

Those are just tracers right

Particles with only convection from fluid and then integrated in time. I never understand why one would want to have those, just for visualization purposes? Or some way to get residence time

yes, and yes. It is uncoupled so the particles don't interact with the fluid but it can be useful if you don't expect particles to have a significant impact on the flow but still want to be able to estimate particle transport (to get residence time, see dead zones where particles might get stuck, etc)

for sure if you expect 2 way particle/flow interactions it would be better to move to a lagrangian solver

(feel free to correct me, I'm no lagrangian expert)

That is how I see it, I did an coupled Lagrangian project without particle-particle interaction to see where particles fly to the wall due to inertia. But then again you include form of a particle force. Good thanks for the refresher

I liked my description better

How do you apply that? I found a function object but how do you now specify where it is applied?

Do you maybe have a file where you used it? Or could you explain how 👉 👈

There is a solver named

icoUncoupledKinematicParcelFoam

which compute the transport of a cloud on a pre-calculated velocity field (computed with whatever other solver) The function object

icoUncoupledKinematicCloud

allows to directly compute the cloud transport when you solve for the flow. You get some informations about it here: https://develop.openfoam.com/Development/openfoam/-/blob/master/src/functionObjects/lagrangian/icoUncoupledKinematicCloud/icoUncoupledKinematicCloud.H

the cloud properties are defined in a

constant/kinematicCloudProperties

file so your best chance is to check tutorials from the

icoUncoupledKinematicParcelFoam

solver to see how it works.

kinematicCloudProperties

can be tricky to setup. I mean there are plenty of stuff in there depending on what you need to do.

Thank you good sir

Anyone know why that particular solver was given a name so... difficult?

typical openfoam layers. There is a

kinematicParcelFoam

and this one is the incompressible uncoupled version You can go deeper with the dynamic mesh variant,

uncoupledKinematicParcelDyMFoam

🙃

this was actually one of the motivation of the foundation branch: refactoring code and decluttering solvers

Well yes, but why wasn't it named shorter like icoC1ParcelFoam? C1 for one-way coupling 🤔 assuming they wanted to reserve naming convention for two and four way coupled versions.. otherwise why not leave "uncoupled" out completely

I guess there is no such naming convention

Maybe it's just that inventing good names is difficult. The "field-based Lagrangian" is also not quite what I'd expect it to be.. anyways we live with what we got 🧑‍🏭

I think they go with full words in general.. You could have icoOnewayCoupledKinematicParcel .. But 1 way is just uncoupled (I think).. 2 way is coupled.. 4 way is called CollidingParcel which is derived from KinematicParcel Beyond Uncoupled, I think it goes into DPMFoam, not sure of the incomprehensible element in that case.. and then intra-parcel features get added in MPPICFoam