CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > ANSYS > FLUENT > Fluent UDF and Scheme Programming

particle (eulerian) cell variable macro name

Register Blogs Members List Search Today's Posts Mark Forums Read

Like Tree2Likes
  • 2 Post By pakk

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   July 13, 2015, 16:04
Default particle (eulerian) cell variable macro name
  #1
Member
 
Casey
Join Date: Jun 2009
Posts: 98
Rep Power: 16
meangreen is on a distinguished road
Hi All,

I am trying to write several UDFs and I found there is a serious lack of "cell variable macro names" in the UDF manuals (and almost anywhere I can look). For example, a cell variable for x-velocity is C_U(c,t). I was hoping someone could help me with the following properties I want to pull OUT of fluent in order to write a UDF. I am using the Eulerian multiphase option.

The properties I am looking for currently are constants, I just want to make sure the UDF can take the information out of Fluent so the user doesn't have to go in and change the UDF every time they want to run a different particle type (i.e. I want it idiot proof).

1. Particle diameter
2. Coefficient of Restitution

I would be happy to start compiling a list of cell variable macro names and posting on updating on the forum.

I have found the granular temperature is C_GT(c,t).

Thanks!
meangreen is offline   Reply With Quote

Old   July 14, 2015, 10:23
Default
  #2
Senior Member
 
Join Date: Nov 2013
Posts: 1,965
Rep Power: 26
pakk will become famous soon enough
Particle diameter is P_DIAM(p), but you can find that one in the manual. Restitution coefficient is a boundary condition property, so may be more difficult to find.

But a more general approach, that you could have used to find out that the granular temperature is C_GT: (I do not claim this is not user-friendly!)
  1. Look in storage.h for the storage variable with the name that comes closest to what you want. In this case: SV_GRANULAR_TEMPERATURE_MEAN.
  2. The internal structure of Fluent is such that you can access the corresponding variable with "C_STORAGE_R(c,t,SV_GRANULAR_TEMPERATURE)". (I don't know how and where the "_MEAN" part is removed, but I have seen that more often.)
  3. If you want to know if there is a shorter name for this, search in the text-files in the "src" folder for "SV_GRANULAR_TEMPERATURE", and if you have the same version as me, you will see in "granular.h" that you can do this with "C_GT(c,t)".

Looking in the header files is a way to find these 'undocumented features' of Fluent.
meangreen and kevinvien like this.
pakk is offline   Reply With Quote

Old   July 14, 2015, 15:18
Default
  #3
Member
 
Casey
Join Date: Jun 2009
Posts: 98
Rep Power: 16
meangreen is on a distinguished road
Thanks Pakk, I am going to give this a try in the next few days. I'll check back with questions if any come up, otherwise I'll list if I find any good results!

Thanks,
Casey
meangreen is offline   Reply With Quote

Old   September 3, 2015, 01:33
Default And the others?
  #4
Senior Member
 
Join Date: Mar 2014
Posts: 375
Rep Power: 13
hwet is on a distinguished road
Quote:
Particle diameter is P_DIAM(p), but you can find that one in the manual. Restitution coefficient is a boundary condition property, so may be more difficult to find.

But a more general approach, that you could have used to find out that the granular temperature is C_GT: (I do not claim this is not user-friendly!)
Look in storage.h for the storage variable with the name that comes closest to what you want. In this case: SV_GRANULAR_TEMPERATURE_MEAN.
The internal structure of Fluent is such that you can access the corresponding variable with "C_STORAGE_R(c,t,SV_GRANULAR_TEMPERATURE)". (I don't know how and where the "_MEAN" part is removed, but I have seen that more often.)
If you want to know if there is a shorter name for this, search in the text-files in the "src" folder for "SV_GRANULAR_TEMPERATURE", and if you have the same version as me, you will see in "granular.h" that you can do this with "C_GT(c,t)".

Looking in the header files is a way to find these 'undocumented features' of Fluent.
Does that mean that for models such as for example the DPM breakup ones, they can be called into a UDF too by looking up in the src folder what fluent calls them?
From an earlier post on this forum I thought that you could not call a breakup model into a UDF and the only way to do it was write the whole breakup model code again in your UDF...
hwet is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[Other] refineWallLayer Error Yuby OpenFOAM Meshing & Mesh Conversion 2 November 11, 2021 11:04
Eulerian - Eulerian and Particle Tracking s.petley CFX 2 April 20, 2015 06:04
injection problem Mark New FLUENT 0 August 4, 2013 01:30
how to get the flux when particle passing through a cell face uvwxyz98765 FLUENT 0 June 11, 2011 00:00
Cells with t below lower limit Purushothama Siemens 2 May 31, 2010 21:58


All times are GMT -4. The time now is 07:33.