[saayo3]

Good day, everyone,

I am using a concatenated udf to define (i). flow profiles at velocity-inlet boundary named 'inlet, & (ii). profile for Roughness Constant, Cs, on the floor boundary named 'wall-floor' of a domain.

The program is to be sent from my windows PC to a remote Linux system.

I have written the following journal file to compile & load the udf, and define & initialize conditions at the velocity-inlet & wall boundaries:

file/read-case fluent.cas
define/user-defined/compiled-functions compile
"libudf"
yes
"inlet.c" "" ""
define/user-defined/compiled-functions load
"libudf"
define/boundary-conditions/velocity-inlet inlet no no yes yes yes yes "udf" "inlet_x_velocity::libudf" no 0 yes yes yes "udf" "k_profile::libudf" yes yes "udf" "dissip_profile::libudf"
define/boundary-conditions/wall wall-floor no no no 0.211 yes yes "udf" "Cs::libudf"
solve/initialize/compute-defaults/velocity-inlet/inlet
solve/initialize/compute-defaults/wall/wall-floor
solve/init/initialize-flow
solve/iterate 5000
file/binary-files n
file/confirm-overwrite n
file/write-data fluent.dat
exit
y

But I continued to get the following error message each time I tried to run the program:

"Warning: An error or interrupt occurred while reading the journal file. Some commands may not have been completed.

> Halting due to end of file on input".

Please, could someone, kindly, help me point out the error(s) and edit the journal file as appropriate.

Thanks so much, in anticipation of the kind gesture.


Samuel

[Hershey]

I would suggest stepping through your journal file manually and seeing if the commands you are issuing in the journal file are exactly as FLUENT is asking for.

I usually encounter a problem like this when my journal file doesn't anticipate an extra "yes" or "no" input and thus my journal file keeps running until the end without giving proper instructions to FLUENT.

Your journal file is not long at all, so just start FLUENT and type in each line one at a time. If there are any discrepancies, then correct them.

My guess is that the confirm overwrite command is giving you issues if there is no file that needs to be overwritten.