You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here, `arguments` is the `input_validator_args` key in the [test data configuration](#test-data-configuration) and [test case configuration](#test-case-configuration).
1269
+
Here, `arguments` is the `input_visualizer_args` key in the [test data configuration](#test-data-configuration) and [test case configuration](#test-case-configuration).
1270
1270
1271
1271
Note that the visualizer would not typically be invoked by the judging system, the invocation instructions are mainly provided to ensure consistency between problem development tools.
1272
1272
1273
1273
## Output Visualizer
1274
1274
1275
1275
An output visualizer is an optional [program](#programs) that is run after every invocation of the output validator in order to generate images illustrating the submission output.
1276
-
A visualizer program must be an application (executable or interpreted) capable of being invoked with a command line call. It is invoked using the same arguments as the output validator, except that `output_validator_args` is replaced with `output_visualizer_args`.
1276
+
An output visualizer program must be an application (executable or interpreted) capable of being invoked with a command line call. It is invoked using the same arguments as the output validator, except that `output_validator_args` is replaced with `output_visualizer_args`.
1277
1277
It must be provided as a program (as specified [above](#programs)) in the directory `output_visualizer/`.
1278
1278
1279
1279
All files written to the feedback directory by the output validator are accessible to the visualizer.
0 commit comments