Replies: 1 comment
-
Hi @TFiFiE, From a code standpoint, CAM16 almost entirely piggyback on CIECAM02, if you look at the module imports it is quite significant. I prefer the separation of concerns, makes the code a bit more manageable and importantly, CAM16 is not CIECAM16, it is not blessed by the CIE, so I would rather keep it separate. Hope that makes sense. Cheers, Thomas |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Would it be in the scope of this project to consolidate as much as CIECAM02 and CAM16 have in common in a single codebase and make explicit exactly how they differ?
Beta Was this translation helpful? Give feedback.
All reactions