Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dinamica_console [2026/07/06 19:13] hermann created |
dinamica_console [2026/07/11 22:00] (current) hermann |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| * ''-granularity=[granularity]'' — Override the default granularity multiplier value used to break jobs into parallel tasks. | * ''-granularity=[granularity]'' — Override the default granularity multiplier value used to break jobs into parallel tasks. | ||
| * ''-propagate-exceptions'' — Propagate top-level exceptions instead of only reporting them and exiting. | * ''-propagate-exceptions'' — Propagate top-level exceptions instead of only reporting them and exiting. | ||
| - | * ''-disable-submodel-expansions'' — Disable submodel expansions before running the script. | + | * ''-disable-submodel-expansions'' — Disable submodel expansions before running the script. See [[submodels#submodel_expansion_and_execution|Submodel Expansion and Execution]] for details on what expansion does. |
| * ''-disable-copy-optimization'' — Disable data copy optimization during script execution. //Only use this setting if you know what you are doing//. | * ''-disable-copy-optimization'' — Disable data copy optimization during script execution. //Only use this setting if you know what you are doing//. | ||
| - | * ''-remove-redundant-carriers'' — Remove all unnecessary intermediate carrier functors before executing a model. | + | * ''-remove-redundant-carriers'' — Remove all unnecessary intermediate carrier functors before executing a model. See [[submodels#submodel_expansion_and_execution|Submodel Expansion and Execution]] for details. |
| * ''-dont-run'' — Parse and validate the model script, but do not execute it. Useful together with ''-output'' to only convert a script. | * ''-dont-run'' — Parse and validate the model script, but do not execute it. Useful together with ''-output'' to only convert a script. | ||
| Line 38: | Line 38: | ||
| * ''-log-level=[log-level]'' — Set the execution log level. Values: ''UNCONDITIONAL=0'', ''ERROR=1'', ''WARNING=2'', ''RESULT=3'', ''INFO=4'', ''INFO2=5'', ''DEBUG=6'', ''DEBUG2=7''. Note that this controls the volume of messages generated, not performance. | * ''-log-level=[log-level]'' — Set the execution log level. Values: ''UNCONDITIONAL=0'', ''ERROR=1'', ''WARNING=2'', ''RESULT=3'', ''INFO=4'', ''INFO2=5'', ''DEBUG=6'', ''DEBUG2=7''. Note that this controls the volume of messages generated, not performance. | ||
| - | * ''-log-subsystem=[log-subsystem]'' — Set the execution log subsystem flags, restricting debugging information to specific subsystems. Only takes effect when ''-log-level'' is set to ''DEBUG'' or ''DEBUG2''. Values are bit flags that can be combined by summing them: ''GENERAL=1'', ''OPENCL=2'', ''SCRIPT_READER_WRITER=4'', ''FUNCTOR_SCHEDULER=8'', ''FUNCTOR_DEPENDENCE_GRAPH=16'', ''FUNCTOR_EXECUTION=32'', ''FILESYSTEM=64'', ''MAP_IO_HANDLER=128'', ''FUNCTOR_COPY_ANALYSIS=256'', ''SYSTEM=256''. | + | * ''-log-subsystem=[log-subsystem]'' — Set the execution log subsystem flags, restricting debugging information to specific subsystems. Only takes effect when ''-log-level'' is set to ''DEBUG'' or ''DEBUG2''. Values are bit flags that can be combined by summing them: ''GENERAL=1'', ''OPENCL=2'', ''SCRIPT_READER_WRITER=4'', ''FUNCTOR_SCHEDULER=8'', ''FUNCTOR_DEPENDENCE_GRAPH=16'', ''FUNCTOR_EXECUTION=32'', ''FILESYSTEM=64'', ''MAP_IO_HANDLER=128'', ''FUNCTOR_COPY_ANALYSIS=256'', ''SUBMODEL=512'', ''EXECUTION_BASICS=1024'', ''GRAPHICAL_INTERFACE=2048'', ''DATABASE=4096'', ''TABLE_IO_HANDLER=8192'', ''MAP_HANDLING=16384'', ''TABLE_HANDLING=32768'', ''SYSTEM_COMMUNICATION=65536''. |
| * ''-beep'' — Beep to indicate that the execution has completed. | * ''-beep'' — Beep to indicate that the execution has completed. | ||
| + | |||
| + | During execution, the console only displays messages at the ''INFO2'' level and below, regardless of the configured ''-log-level''. Each worker also writes its own log file, named ''log_X.txt'' (where ''X'' is the worker number), which mirrors what the console shows: only messages at the ''INFO2'' level and below, even if a ''DEBUG''/''DEBUG2'' level is configured. When debug information is enabled, it is written separately to a per-worker file named ''debug_X.txt'' instead, following the same naming scheme; ''DEBUG'' and ''DEBUG2'' messages never appear in ''log_X.txt'' or on the console. Both the log and debug files are created in the same folder as the model script being executed. | ||
| ===== Metadata ===== | ===== Metadata ===== | ||
| Line 104: | Line 106: | ||
| <code> | <code> | ||
| DinamicaConsole -log-level=6 -log-subsystem=8 "C:\models\my_model.ego" | DinamicaConsole -log-level=6 -log-subsystem=8 "C:\models\my_model.ego" | ||
| + | </code> | ||
| + | |||
| + | Run a model script at the Debug level, logging multiple subsystems at once by summing their flags — here, ''GENERAL=1'' + ''FUNCTOR_SCHEDULER=8'' + ''MAP_IO_HANDLER=128'' = ''137'': | ||
| + | |||
| + | <code> | ||
| + | DinamicaConsole -log-level=6 -log-subsystem=137 "C:\models\my_model.ego" | ||
| </code> | </code> | ||