AcademySoftwareFoundation/rawtoaces

Summary tests/testIDT.cpp embeds large numeric table literals next to tests that already load rawtoaces_data JSON under DATA_PATH. That duplicates on-disk data, bloats the file (thousands of lines), and is hard to review. This work replaces those patterns with lighter assertions: spot-checks for loaded fixtures, and fingerprints for transformation outputs. Background (for newcomers) These tests exercise IDT-related loading and math. The intended reader is someone picking up a day-sized task (for example during ASWF Dev Days) who may not have touched this suite before. The goal is to preserve regression coverage while making testIDT.cpp easier to maintain—without adopting snapshot-testing tooling. Where to look tests/testIDT.cpp — large double / table literals interleaved with OIIO_CHECK_* assertions. Fixture root: DATA_PATH → ../_deps/rawtoaces_data-src/data/ (camera, CMF, and related JSON). Search for big brace-initialized arrays and loops comparing every row to a literal. Sug

Summary Prefer non-throwing std::filesystem overloads (those taking std::error_code) instead of overloads that throw std::filesystem::filesystem_error. Then remove the try/catch around input existence checks in ImageConverter::process_image, mapping errors to existing Status / last_error_message behaviour. More broadly, apply noexcept where it is correct and consistent with the project’s style—especially on helpers that cannot throw after this migration. Background (for newcomers) The comment near process_image mentions catching filesystem exceptions (e.g. on Windows). The C++ standard library allows querying filesystem operations with an error_code instead of exceptions. This issue is about error handling style: avoid exception-based control flow for expected filesystem failures where possible, keep user-visible errors aligned with current enums/messages, and document any platform nuance. Where to look src/rawtoaces_util/image_converter.cpp — process_image try/catch around std:

Summary XYZ_to_color_temperature interpolates in mired space (using robertson_mired_table), converts the result to Kelvin via mired_to_kelvin, clamps, and returns Kelvin. Downstream code often immediately converts that Kelvin value back to mired with kelvin_to_mired (for example when weighting matrices). That is an extra round-trip that may be unnecessary or lossy from a numerical/design standpoint. Background (for newcomers) Correlated color temperature (CCT) appears both as Kelvin and as mired (micro reciprocal Kelvin, (10^6/\mathrm{K})) in this codebase. Helpers live in src/rawtoaces_core/rawtoaces_core.cpp: kelvin_to_mired, mired_to_kelvin, and XYZ_to_color_temperature. Some call sites take XYZ → CCT (Kelvin) → mired again within the same workflow. This issue asks for a design cleanup (and tests as appropriate): clarify whether the Kelvin return is the right API, whether some paths should stay in mired until later, or whether the duplication is intentional and should be documen