Interpreted UDFs are interpreted from source files using the graphical user interface, but in a single-step process. The process, which occurs at runtime, involves using the Interpreted UDFs dialog box, where you a source file.
Inside ANSYS Fluent, the source code is compiled into an intermediate, architecture-independent machine code using a C preprocessor. This machine code then executes on an internal emulator, or interpreter, when the UDF is invoked. This extra layer of code incurs a performance penalty, but enables an interpreted UDF to be shared effortlessly between different architectures, operating systems, and ANSYS Fluent versions. If execution speed does become an issue, an interpreted UDF can always be run in compiled mode without modification.
The interpreter that is used for interpreted UDFs does not have all of the capabilities of a standard C compiler (which is used for compiled UDFs) and does not support all parallel UDF macros. For a detailed summary of limitations, see Limitations.
Note: In some situations you may encounter an error with interpreted UDFs related to the C
preprocessor (CPP) distributed with Fluent. As a workaround, you can enter the full path to
the system's preprocessor in the CPP Command Name field in the
Interpreted UDFs dialog box; for example,
/usr/bin/cpp or gcc -E (Linux only).