From 838dd34eb17b0d59826757c11383a00d3b89f86a Mon Sep 17 00:00:00 2001 From: aejjeh <aejjeh@illinois.edu> Date: Tue, 21 Jan 2020 11:54:08 -0600 Subject: [PATCH] Update cava readme --- hpvm/test/hpvm-cava/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/hpvm/test/hpvm-cava/README.md b/hpvm/test/hpvm-cava/README.md index 5b24829767..890b629d17 100644 --- a/hpvm/test/hpvm-cava/README.md +++ b/hpvm/test/hpvm-cava/README.md @@ -13,8 +13,8 @@ After building HPVM, the following steps are required to build and run the camer 1. Build with `make TARGET=seq` for CPU and `make TARGET=gpu` for gpu. 2. Run with `./cava-visc-<Target> example-tulip-small/raw_tulip-small.bin example-tulip-small/tulip-small`. - * `<Target>` can be either `seq` or `gpu` depending on what target is used to build. - * This processes the raw image `example-tulip-small/raw_tulip-small.bin`. Note that raw images are different from bitmaps, so you might need to obtain them using special software. - * This generates: `tulip-small.bin` and `tulip-small-<stage>.bin` where `<stage>` represents the stage of the pipeline. + * `<Target>` can be either `seq` or `gpu` depending on what target is used to build. + * This processes the raw image `example-tulip-small/raw_tulip-small.bin`. Note that raw images are different from bitmaps, so you might need to obtain them using special software. + * This generates: `tulip-small.bin` and `tulip-small-<stage>.bin` where `<stage>` represents the stage of the pipeline. 3. Convert the binary outputs to a PNG with `./convert.sh example-tulip-small` 4. View the resulting PNG at `example-tulip-small/tulip-small.png`. (As well as all the intermediary images for each stage `tulip-small-<stage>.png`) -- GitLab