|October 22, 2013, 14:09||
Join Date: Nov 2012
Posts: 7Rep Power: 5
I have some doubts regarding DEFINE_INIT, mainly its priority in Fluent's algorithm and its application.
Here's my case:
A UDF (with DEFINE_INIT) allows initilisation of a sub domain's thread VOF value. This is seen in display-contour-vof. Next, when a calculation is run with this value, even for a single time step, the value of VOF reverts back to its default value in the solution initialisation box. This should not be the case.. the calculation should continue with the UDF initialised VOF value. What am I missing?
Any ideas? Thanks in advance!
|define_init, udf, vof|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Installing OF 1.6 on Mac OS X||gschaider||OpenFOAM Installation on Windows, Mac and other Unsupported Platforms||129||June 19, 2010 09:23|
|Missing math.h header||Travis||FLUENT||4||January 15, 2009 12:48|
|REAL GAS UDF||brian||FLUENT||6||September 11, 2006 08:23|
|Free surface boudary conditions with SOLA-VOF||Fan||Main CFD Forum||10||September 9, 2006 12:24|
|UDF FOR UNSTEADY TIME STEP||mayur||FLUENT||3||August 9, 2006 10:19|