[surya.tdr]

Hi,
As DPM considers particle as point masses, I need to get the size so that I can give a trap on the wall when it actually hits it and not when its center hits.

My idea is to track the distance between the center of incoming particles and wall, and to write a udf such that when that distance equals the radius of particle, the particle is trapped. So what udf macro I need to write whether it is define_dpm_boundary condition? Kindly help me to get some light in to this problem.

[vinerm]

Could you describe the objective of doing that? It would be little cumbersome to implement since DEFINE_DPM_BC works on the particles that hit that particular BC. You need to identify the particles within close proximity. Now, if you have 100 mesh faces on the boundary and there are 100 particles, if I'm not wrong, you have to loop through 10000 cycles to do this. But its doable.

[surya.tdr]

Thanks for your reply.

My objective is for incorporating a mechanism called interception in particle filtration by fibrous filters where particles follows the streamline and gets trapped when its distance from the obstacle (wall) is equal to the radius of the particle. I am doubtful about the macro which is to be used.

[vinerm]

It can be done using standard macros, however, the difficulty lies with the topology of the filter. If the filter is planar, then it is rather easy. If the normal of the filter is aligned with one of the coordinate axes, you can track the positions of the particles and then either trap them or remove them as soon as those are within the limits prescribed as the distance between filter position and particle position being lesser than or equal to radius.

Now about macros, as far as DEFINE_ macro is concerned, you can use any of those that provide you with Tracked_Particle as the argument, such as, DEFINE_DPM_OUTPUT or DEFINE_DPM_SCALAR_UPDATE. Within these macros, you can check the positions using P_POS. Assuming the position of the filter is a known value, comparison is easy. Well, it is always known, the problem becomes little involved if the position is varying across the space, i.e., filter has some arbitrary shape. Procedure would still be same though. To trap, remove, or reflect a particle, you can use macro MARK_PARTICLE.

[surya.tdr]

The geometry is like 2-D planar. Its like flow past a large number of cylinders (fibers) and the particles has to be trapped on these cylinders. Thank you for your information. If possible can you share any of such examples of particle tracking as I am new to udf.

Thank you

[vinerm]

Look at the following

https://www.afs.enea.it/project/nept...udf/node65.htm

[surya.tdr]

Thank you so much.

[vinerm]

You forgot to attach the file

[pakk]

For DPM to be useful, you have to assume that your particles are small enough compared to the geometry. If your particle is so big that it matters whether the center of the particle hits the wall or the outside of the particle, you should not be using the DPM method, but a different method that explicitly includes the shape of the particle, such as 6DOF.


So there are two possibilities:
1. You don't need this, ignore the small difference between particle center and particle edge. You don't need this UDF.
2. You should not use the DPM method. You don't need this UDF.

[vinerm]

There are multiple issues with the code. Let me start from the bottom. You forgot to end particle_cell_loop. Anything with a begin in Fluent is supposed to have an end.

You cannot return anything in this macro since it is supposed to return void, i.e., nothing. So, remove return part. return PATH_ACTIVE can be used only inside DPM_BC or some other code that expects an integer return value.

REMOVED with remove the particles as if those were never there. If you want that, it is alright. Usually, the material of the particles is added either to the wall as a deposition or to the continuous fluid. Disappearance is not physical. So, do something with the particle before removing it.

C is different from, say python; you have to use braces around test condition after if, i.e., (pc-bc <= P_DIAM(tp)/2)

There is no macro called P_CENTROID. Use P_POS. Y has to be declared before use. No declaration within the function, such as, cell_t c. No need to define diameter if you are using P_DIAM as it is in equations downstream. And DO NOT use common variables as diameter. Those might conflict with Fluent defined variables.

No need to fetch Thread *t, because it is already provided by Fluent as f in your code. But note that f is not the thread of just any boundary; rather it refers to the boundary selected in Sampling Window.

For the whole code, do note that the names of the variables do not matter; what they mean is important. Since you use f as second last argument does not mean you can use it as face_t in F_CENTROID. Go through the manual to understand the meaning of each argument that DEFINE_DPM_OUTPUT has.

Do not define variables outside DEFINE_, until you need global variables. Since you have only one DEFINE_, you do not need any global variables.

No need to include dpm.h. It is already included in udf.h

[surya.tdr]

I will look in to it. Thanks a lot. I will correct and share the udf once more.

[vinerm]

If you are using DEFINE_DPM_BC, then you should use path abort for ensuring that the particle gets trapped. Path active is meant for the particles that are still in the domain and need to be tracked further. All the particles are shown within the particle tracking. However, the trapped ones are shown as trapped in the text window. Those are not visible in the graphics since their paths get aborted. If you want to see how many particles got trapped on a particular boundary, you can do sampling on that particular boundary.

[Achini]

Originally Posted by vinerm

It can be done using standard macros, however, the difficulty lies with the topology of the filter. If the filter is planar, then it is rather easy. If the normal of the filter is aligned with one of the coordinate axes, you can track the positions of the particles and then either trap them or remove them as soon as those are within the limits prescribed as the distance between filter position and particle position being lesser than or equal to radius.

Now about macros, as far as DEFINE_ macro is concerned, you can use any of those that provide you with Tracked_Particle as the argument, such as, DEFINE_DPM_OUTPUT or DEFINE_DPM_SCALAR_UPDATE. Within these macros, you can check the positions using P_POS. Assuming the position of the filter is a known value, comparison is easy. Well, it is always known, the problem becomes little involved if the position is varying across the space, i.e., filter has some arbitrary shape. Procedure would still be same though. To trap, remove, or reflect a particle, you can use macro MARK_PARTICLE.

Hi vinerm,

I find your replies to this post quite useful.
Can you tell me how to find the distance from particle position to the wall boundary?
Is there a specific macro I an use for that?

Thank you!

[alisaidi]

Hi
I am working to somehow the same problem.
It would be great if you can share your final UDF.
Thanks in advance.

[Wang Cong NEU]

Originally Posted by surya.tdr

I will look in to it. Thanks a lot. I will correct and share the udf once more.

Hi！
The examples you shared are very useful to me. Thank you.Recently, I am conducting research on the interaction between bubbles (represented by DPM particles), liquid, and gas, and I have encountered two challenging issues.
1. When particles move to the liquid air-contact interface, how to stop tracking particles ,by determining that the gas volume fraction here is greater than or equal to 0.5 (it is considered that particles enter the air).I don't know what Macros will be available.

2. How to add the material and other properties of the particles that have stopped tracking to the continuous phase，I am still new in UDF and do not know what macro to use to implement this function.

I have been troubled for a long time, Could you please share your UDF with my email(wangcong98520@163.com)? Thank you a lot,Kindly.