ID 593441 - CSP LUT files exported from the MatchGrade node can have different contents even if the input images are identical

Problem summary:
CSP LUT files exported from the MatchGrade node can have different contents even if the input images are identical 
 
Customer reported version:
Nuke 15.1v5
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Download the attached match_grade_identical.nk file and launch NukeX.
2) Double click both MatchGrade nodes to open their Properties, and press the Analyze Reference Frames button for each.
3) Then, press the Write button for both MatchGrade nodes to create a CSP file from each.
4) Open the mg_1.csp and mg_2.csp files in a text editor and observe their differences: 
 
mg_1.csp line 19:

0.085872 0.072337 0.072296

mg_2.csp line 19:

0.083307 0.072424 0.072369

 
Expected behavior:
MatchGrade nodes should output identical CSP LUTs if the Source and Target images are unchanged.
 
Actual behavior:
When a MatchGrade exports a CSP LUT, the file's contents are not always consistent even if the pixel values supplied to the Source and Target inputs do not change between setups. 
 
This also occurs when using the MatchGrade node's Mask option, so slightly different .csp files can be output even if the region inside the Mask is completely identical and hasn't changed. 
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
NukeX 15.1v5 - Windows 10, macOS 14 Sonoma
NukeX 14.0v1 - Windows 10
NukeX 13.0v1 - Windows 10
NukeX 12.0v1 - Windows 10
 
Earliest version tested:
NukeX 12.0v1 - This issue appears to be in all tested versions of the product