Redirecting Khiops Output to Standard Streams
When Khiops runs in batch mode, its command trace, log messages, and progression messages can be written to standard output or standard error instead of separate files. This is useful when Khiops is launched from a script, a container, or another application that collects process output.
The -e, -t, and -o options accept an output path:
-ewrites log messages;-twrites progression messages;-owrites the commands recorded while the scenario is replayed.
Unix-like systems
Use /dev/stdout to send an output stream to standard output:
This command replays scenario.prm in batch mode and sends all three output streams to standard output. The output contains entries from the command, log, and progression streams, for example:
Khiops.command // 2026-07-03 16:56:26
Khiops.command // khiops
Khiops.command // -> Khiops
Khiops.command ClassManagement.OpenFile // Open...
Khiops.log Train supervised model for classification of target variable class
Khiops.progression 2026-07-03 16:56:27 progression_start
Khiops.progression 2026-07-03 16:56:27 Completed task 1 Database basic stats Initialization
Khiops.progression 2026-07-03 16:56:27 progression_stop
When the output is redirected to a standard stream, Khiops prefixes each line with the stream that produced it:
Khiops.commandidentifies the command trace redirected with-o;Khiops.logidentifies the log messages redirected with-e;Khiops.progressionidentifies the progression messages redirected with-t.
To send the output to standard error instead, use /dev/stderr:
Each option can also be directed to a different stream. For example, the following command keeps logs on standard error while leaving the command trace and progression messages on standard output:
Windows
On Windows, use the CON device to send the output to the console: