Fix default orientation and box white balance#268
Fix default orientation and box white balance#268remia wants to merge 2 commits intoAcademySoftwareFoundation:mainfrom
Conversation
Signed-off-by: Rémi Achard <remiachard@gmail.com>
Signed-off-by: Rémi Achard <remiachard@gmail.com>
|
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (60.00%) is below the target coverage (70.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #268 +/- ##
=======================================
Coverage 90.77% 90.77%
=======================================
Files 17 17
Lines 3446 3446
Branches 532 532
=======================================
Hits 3128 3128
Misses 318 318
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
Is there a way we can have a regression tests for changed functionality? Also, this feels like a breaking API move basically - changing default behaviour. |
|
I'm not sure there is an easy to test this but will have a look at the test suite. Also yes this changes behaviour, considering these are bug fix so hopefully this is for the better (the greybox white balance was non functional and the orientation from multiple conversion I tested was wrong, though if some are relying on incorrect orientation metadata in the source file, the latter change might be an issue but for the general case I'd think it's something we want). |
|
I'm afraid there is no easy way to test orientations. We don't have any vertical images in the test suite, and ideally we would need multiple. Implementing generation of fake raw test images is on the road map, but until then there is not much we can do. |
|
Ok, I'll leave this here for the time being then, trying to sort out the CLA thing. |
Description
Proposing the follow minor changes:
Tests
Checklist:
need to update the documentation, for example if this is a bug fix that
doesn't change the API.)
(adding new test cases if necessary).
already run clang-format before submitting, I definitely will look at the CI
test that runs clang-format and fix anything that it highlights as being
nonconforming.