Description
A very minor issue I came across while playing around with HalideTraceViz. The top example in the usage message on L296 uses the -s and -t flags in lieu of --size and --timestamp. Running this on a local pipeline results in the following message:
Argument parsing failed at argument 1
<Usage message>
Just opening an issue with the goal of fixing the error message!
Reproducing case
Using any Halide pipeline, run the following (JIT mode):
HL_TARGET=host-trace_all HL_TRACE_FILE=/dev/stdout <command to make and run pipeline> | \
HalideTraceViz -s 768 1280 -t 10000 \
ffmpeg -f rawvideo -pix_fmt bgr32 -s 768x1280 -i /dev/stdin -c:v h264 output.mp4
How did you get Halide?
Built from source
Halide version
No response
Halide commit (if known)
38c470f
Target
arm-64-osx
Operating system
macOS 26.5
Additional context
Happy to either change the usage message or add short flags for -s and -t`!
Description
A very minor issue I came across while playing around with
HalideTraceViz. The top example in the usage message on L296 uses the-sand-tflags in lieu of--sizeand--timestamp. Running this on a local pipeline results in the following message:Just opening an issue with the goal of fixing the error message!
Reproducing case
Using any Halide pipeline, run the following (JIT mode): HL_TARGET=host-trace_all HL_TRACE_FILE=/dev/stdout <command to make and run pipeline> | \ HalideTraceViz -s 768 1280 -t 10000 \ ffmpeg -f rawvideo -pix_fmt bgr32 -s 768x1280 -i /dev/stdin -c:v h264 output.mp4How did you get Halide?
Built from source
Halide version
No response
Halide commit (if known)
38c470f
Target
arm-64-osx
Operating system
macOS 26.5
Additional context
Happy to either change the usage message or add short flags for
-sand -t`!