A journal file contains a sequence of Fluent commands, arranged as they would be typed interactively into the program or entered through the user interface. The user interface commands are recorded as Scheme code lines in journal files. You can also create journal files manually with a text editor. If you want to include comments in your file, put a semicolon (;) at the beginning of each comment line.
The purpose of a journal file is to automate a series of commands instead of entering them repeatedly on the command line. It can also be used to produce a record of the input to a program session for later reference, although transcript files are often more useful for this purpose (see Creating Transcript Files).
Command input is taken from the specified journal file until its end is reached, at which time control is returned to the standard input (usually the keyboard). Each line from the journal file is echoed to the standard output (usually the screen) as it is read and processed.
Important: A journal file by design is a simple record/playback facility. It contains no information about the state in which it was recorded or the state in which it is being played back.
Be careful not to change the folder while recording a journal file. Also, try to recreate the state in which the journal was written before you read it into the program.
For example, if the journal file includes an instruction for Fluent to save a new file with a specified name, check that no file with that name exists in your directory before you read in your journal file. If a file with that name exists and you read in your journal file, it will prompt for a confirmation to overwrite the old file when the program reaches the write instruction. Because the journal file contains no response to the confirmation request, Fluent will not be able to continue following the instructions of the journal file.
Other conditions that may affect the program's ability to perform the instructions contained in a journal file can be created by modifications or manipulations that you make within the program.
For example, if your journal file displays certain surfaces, you must read in the appropriate mesh file before reading the journal file.
Important: At a given time, only one journal file can be open for recording. But you can read a journal file at any time. You can also write a journal and a transcript file simultaneously.
You can read multiple journal files in one go.
Select the files in the order you want them read in Fluent in the Select File dialog box.
You can also create a journal file that makes calls to other journal files.
The following is an example of such a nested journal file:
/file/read-journal "E:/Example_journals_example1.jou" "" /file/read-journal "E:/Example_journals_example2.jou" "" /file/read-journal "E:/Example_journals_example3.jou" ""
The command /file/set-tui-version enables you to set the
Fluent version for journal files.
While recording a new journal file, the current Fluent version is automatically recorded in the journal file. For example,
/file/set-tui-version "18.2"
While replaying a journal file written in a previous Fluent version, you can set the version it was created in. For example,
/file/set-tui-version "18.1"
Newer arguments (if any) will be skipped and corresponding default settings or values will be used.
To upgrade a journal file written in a previous Fluent version, record the journal while it is run. Older version commands will be recorded as current version commands.
Note: The session version is not modified if you read in a journal file with the
Fluent version set to a previous version (for example,
/file/set-tui-version "18.1"). The current Fluent
version will be restored after the journal replay is complete.
Whether you choose to type the text command in full or use partial strings, complete commands are recorded in the journal files.
Only successfully completed commands are recorded. For example, if you stopped an execution of a command using Ctrl+C, it will not be recorded in the journal file.
If a user interface event happens while a text command is in progress, the user interface event is recorded first.
All default values are recorded.
To start the journaling process, select > > . Enter a name for the file in the Select File dialog box. The journal recording begins and the menu item becomes menu item. You can end journal recording by selecting , or by exiting the program.
You can read a journal file into the program using the Select File dialog box invoked by selecting > > .
Journal files are always loaded in the main (top-level) text menu, regardless of where you are in the text menu hierarchy when you invoke the read command.