ID 562534 - The Camera node can calculate incorrect vertical Window Translate values when reading Alembic files from third party applications

Problem summary:
The Camera node can calculate incorrect vertical Window Translate values when reading Alembic files from third party applications
 
This issue may also affect the New 3D System Camera node (Camera4)

 
Customer reported version:
Nuke 15.0v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke and create a Camera3 node in the Node Graph.
2) In the Camera's Properties, enable the read from file knob and load the attached camera_offset_test.abc file.
3) Duplicate the Camera node, open its File tab, and switch the node name to the second camera:

4) View the Camera nodes, and observe how the edges are partially overlapping. When the cameras are imported in other applications (such as Blender), they are correctly aligned at the corner instead:

 
Expected behavior:
When an Alembic camera has a window translate/film offset/lens shift value, Nuke should produce the same camera frustum as the exporting application and other importing applications.
 
Actual behavior:
The camera frustum inside Nuke doesn't match the results from the other applications (such as Blender or Maya) on the vertical axis.
 
Workaround:
No known workaround at this time
 
Reproduced by Support in:
Nuke 15.0v2 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
 
Earliest version tested:
Nuke 13.0v1- This feature (Camera3 node) did not exist before this version