Improvement in HDR Tutorial – Clarifying Gamma Correction (Fix for Issue #22219)

Projects
, ,
1

Hello everyone,
My name is Jay Pol, a C++ and Python developer passionate about computer vision and OpenCV.
I recently explored the HDR imaging tutorials and noticed that the gamma correction step could be confusing for new users — especially when comparing the results with default tone mapping values.

After reading through Issue #22219, I created a pull request that improves the documentation of the HDR tutorial by clarifying the correct gamma correction usage.

Summary of My Contribution:

  • Added a note explaining that cv.createTonemap() has a default gamma of 1.0.

  • Explicitly set gamma=2.2 in the example to match standard display brightness and ensure consistent results.

  • Updated the tutorial text and code comments for better readability and reproducibility.

  • The change was tested with both Debevec and Robertson tone mapping methods.

You can check my pull request here:
PR #XXXXX – Clarify Gamma Correction in HDR Tutorial
(Fixes #22219)

Why I’m Sharing This Here:
I wanted to engage with the OpenCV community, get feedback from experienced contributors, and learn best practices for writing clearer tutorials and documentation.
I’m also very interested in Google Summer of Code (GSoC 2026) with OpenCV, and I’m eager to contribute to more meaningful features in the image processing and HDR pipeline.

If anyone could share advice on:

  • Improving my PRs for OpenCV standards

  • Getting involved early with GSoC proposal preparation

  • or other areas where I can meaningfully contribute

  • I’d love to hear your thoughts!

Thank you,
Jay Pol
(OpenCV Contributor | Aspiring GSoC Participant 2026)