[majid_kamyab]

Hello
please help

I have asked some CFD experts in my faculty about compiling and I have used both visual studio 2010 and 2013 so I know the routine compiling method
I have tried on many computers and many people in our faculty have tried to compile it but all of the attempts were all unsuccessful
my system type is 64-bit OS
I have interpreted the code and there are no problems in interpreting but calculation diverges due to floating point exception
the error is
The UDF library that you are trying to load (libudf) is not compiled for parallell use on the current platform (win64)
the operation completed successfully
E:\MESH\udf\libudf\win64\3ddp_host\libudf.dll


here is the code

#include "udf.h"

DEFINE_MASS_TRANSFER(mass_tran, c, t, from_index, from_species_index, to_index, to_species_index)
{
Thread *gas = THREAD_SUB_THREAD(t, to_index);
Thread *liq = THREAD_SUB_THREAD(t, from_index);
real m_lg, k_l, dal, usg, kappa, m, c_sat, a;
dal = 1.46*0.000000001;
usg = 0.294188;
kappa = 0.000484011 / 748;
m = 1.204;
a = 2.287843;
k_l = 2 * sqrt((dal / 3.1415)*sqrt(usg*9.8 / kappa));
m_lg = k_l*a*(C_YI(c, liq, from_species_index) - m*C_YI(c, gas, to_species_index));
return (m_lg);
}

[pakk]

If you see:

The UDF library you are trying to load (...\Fluent\libudf) is not compiled ...

It means that the UDF did not compile. People ask this question all the time, but the answer is right there, just read the text.

Something went wrong when you tried to compile it. Look at the text that was written on the screen when you tried to compile, that will give a hint about what was wrong.

[majid_kamyab]

Originally Posted by pakk

If you see:


It means that the UDF did not compile. People ask this question all the time, but the answer is right there, just read the text.

Something went wrong when you tried to compile it. Look at the text that was written on the screen when you tried to compile, that will give a hint about what was wrong.

I know it did not... and thats why I posted this thread.
Ive found the problem.
the udf file was saved in this form masstr.C
but it must be saved in this form masstr.c
please note that the c must be written in lowercase.

[pakk]

Good that you found it. But for next time: it is more useful to include the error you get when compiling, than to include the error you get when loading.

[ghost82]

Originally Posted by majid_kamyab

I know it did not... and thats why I posted this thread.
Ive found the problem.
the udf file was saved in this form masstr.C
but it must be saved in this form masstr.c
please note that the c must be written in lowercase.

So, this means that .C (uppercase) can be interpreted but not compiled?

[majid_kamyab]

Originally Posted by pakk

Good that you found it. But for next time: it is more useful to include the error you get when compiling, than to include the error you get when loading.

I did not understand what you mean?
do you mean when I built the library?
or load the file?

[majid_kamyab]

Originally Posted by ghost82

So, this means that .C (uppercase) can be interpreted but not compiled?

well I could have interpreted it ... It did not work correctly and diverged due to floating point exception. as I am not a programmer or computer engineer I cant say for sure but why do we have to risk when we know .c is correct

[ghost82]

You wrote:
I have interpreted the code and there are no problems in interpreting

I'm assuming you interpreted the .C (uppercase file).
Then you wrote that when you compiled the .C file you had error.

So this means the .C uppercase extension file can be successfully interpreted but not compiled?

PS:
Floating point error is independent from successfully interpreting/compiling.

[pakk]

Originally Posted by majid_kamyab

I did not understand what you mean?
do you mean when I built the library?
or load the file?

When you build. (In this context, build is the same as compile.)
That is the place where something went wrong, so there you can find information to solve the problem.

[majid_kamyab]

Originally Posted by ghost82

You wrote:
I have interpreted the code and there are no problems in interpreting

I'm assuming you interpreted the .C (uppercase file).
Then you wrote that when you compiled the .C file you had error.

So this means the .C uppercase extension file can be successfully interpreted but not compiled?

PS:
Floating point error is independent from successfully interpreting/compiling.

are you sure about the in-dependency of the divergence from interpreting?