Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Benchmark-xl producing different output depending on parameters called. SSIMULACRA2 missing when --print_details_csv used. #3585

Closed
kkthompson opened this issue May 14, 2024 · 0 comments · Fixed by #3589
Labels
unrelated to 1.0 Things that need not be done before the 1.0 version milestone

Comments

@kkthompson
Copy link

Describe the bug
benchmark_xl --print_details_csv does not output the SSIMULACRA2 score as expected. However, --print_details without the csv does output it as expected.

To Reproduce
benchmark_xl --print_details_CSV --encode_reps=1 --decode_reps=1 --input "./*.png" --codec jxl:7:d1 outputs the follow headers:
method,image,error,size,pixels,enc_speed,dec_speed,bpp,dist,psnr,p,bppp,qabpp
Default output has these headers:
Encoding kPixels Bytes BPP E MP/s D MP/s Max norm SSIMULACRA2 PSNR pnorm BPP*pnorm QABPP Bugs

--print_details outputs the following columns
jxl:7:d1 example.png error:0 size: 44264 pixels: 401408 enc_speed:1.97544563 dec_speed:43.35366785 bpp:0.88217474 dist:1.50978231 psnr:43.85183584 ssimulacra2:87.72 p:0.53096151 bppp:0.46840084 qabpp:1.33189174

Expected behavior
Would be great if the headers matched and were in the same order in each output.

Screenshots
N/A

Environment

  • OS: macOS Sonoma 14.4.1
  • Compiler version: n/a
  • CPU type: M1 Max
  • cjxl/djxl version string: benchmark_xl v0.10.2 0.10.2 [NEON]

Additional context
N/A

@mo271 mo271 added the unrelated to 1.0 Things that need not be done before the 1.0 version milestone label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unrelated to 1.0 Things that need not be done before the 1.0 version milestone
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants