ID 162669 - DeepRead node bounding box not lining up correctly with Read node equivalent

Problem summary
When working with Deep data as an exr format, there are two ways that you can import it into Nuke depending on workflow. You can either using a 'Read' node to import as 2D data (with the Deep data embedded) or just as Deep data using the 'DeepRead' node.

If this Deep exr has a bounding box on import (or created in the script), when comparing the 'Read' to the 'DeepRead' node, the bounding box differs.

Customer reported version
nuke.11.0v1

Customer reported platform
centos6

Steps to reproduce

Open attached script and compare the results of the two streams from the reformats

or

1) Import an exr file that has both RGB data and deep data, using a 'Read' node

2) Import an exr file that has both RGB data and deep data, using a 'DeepRead' node

3) Create a 'Reformat' under the 'Read' node, altering the scale to '0.5', resize type to 'none' and ensuring the 'preserve bounding box' is 'on'

4) Create a 'DeepReformat' under the 'DeepRead' node, altering the scale to '0.5', resize type to 'none' and ensuring the 'preserve bounding box' is 'on'

5) Compare the reformat results in the viewer

Result: The bounding box sizes between the two streams differs depending on input

Note: The correct bounding box is the 'Read' nodes bounding box.

Workaround
There are two possible workarounds depending on workflow by copying the bounding box information from the source RGB to the Deep stream:

1) If you are converting from deep back to 2d before rendering, you can simply add a 'CopyBBox' from the source under the 'DeepToImage' node.

2) If you are looking at retaining the data as deep, you can convert the deep to 2d, using a 'DeepToImage' node, then add in the CopyBBox in 2d and then convert from 2d back into deep data using a 'DeepFromImage' node.

Reproduced by support

This bug has been reproduced in:
Nuke 11.1v2 - Windows 7

Nuke 11.1v1 - Windows 7

Nuke 10.5v7 - Windows 7

Nuke 10.5v1 - Windows 7

Nuke 10.0v6 - Windows 7

Nuke 10.0v1 - Windows 7

Nuke 9.0v9 - Windows 7

Nuke 9.0v1 - Windows 7

Nuke 8.0v7 - Windows 7

Nuke 8.0v1 - Windows 7

Unable to reproduce bug in:
Nuke 7.0v10 - Windows 7

Earliest version tested
Nuke 7.0v10 
- Reading in deep data through a Read node was not possible in this version and earlier

Expected behaviour
When importing deep exr files that contain bounding box information (or bounding box information is created within the comp), the bounding box size should remain the same when imported through a 'Read' node or a 'DeepRead' node.

Actual behaviour
The bounding box information varies when importing a deep exr if it is a 'DeepRead' compared to a 'Read'.