ID 373543 - S-Log2 expects scaled ranged data which is inconsistent with S-Log1 and S-Log3

Problem summary
S-Log2 is scaled to expect 'IRE' range data, whereas S-Log1 and S-Log3 expect unscaled code values; this inconsistency is potentially confusing to users.

In addition, S-Log2 is inconsistent with all the S-Logs in OCIO ACES 1.0.3 which also expects unscaled code values as the input to the Sony IDTs. Therefore OCIOColorSpace (ACES 1.0.3 config) and Nuke's built-in ColorSpace node match for S-Log1 and S-Log3, but it is necessary to apply a legal-to-full scale before a ColorSpace node to make it match OCIOColorSpace for S-Log2.

Customer reported version
nuke.11.2v3

Customer reported platform
OS X 10.07

Steps to reproduce

Open the attached .nk script which demonstrates the issue.

Reproduced by support

Reproduced by development team.

Expected behaviour
The OCIOColorSpace (ACES 1.0.3 config) and Nuke's built in ColorSpace node match for S-Log2.

Actual behaviour
S-Log2 is scaled to expect 'IRE' range data, whereas S-Log1 and S-Log3 expect unscaled code values.