ApplyRGB should honor Numpy internal matrix storage order #2075
Labels
Bug
Unwanted or incorrect behavior in currently available functionality.
good first issue
Standard label for new developers to locate good issues to tackle to learn about OCIO development.
help wanted
Issues that the TSC has decided are worth implementing, but don't currently have the dev resources.
Python
Issues that involve majority python development (vs C++).
Numpy matrices may be stored in either row-major or column-major order. The user is typically not aware of the order being used, especially since some Numpy operators swap the order if it is more efficient for them. For example, transpose simply swaps the ordering flag rather than moving numeric values.
The applyRGB function in OCIO essentially just flattens the input and expects channel-interleaved ordering. Ideally, applyRGB would check the storage order and transpose values, if needed. At a minimum, it should issue a warning if the storage order is not as expected.
The text was updated successfully, but these errors were encountered: