10-03-2024 03:27 PM
I'm seeing an issue where if I set the color map outside the representational range of the data type, I see some colors being saturated. If I use a different numeric representation, the pixels in the intensity graph appear normally. I'm using LV2020 64 bit.
10-04-2024 03:19 AM
I'm not entirely sure if it's a bug or an artifact...
The interpolation algorithm that is used, is basically not defined.
I suspect the interpolation does something that's not really expected.
The white that shows isn't the white in the color table, it's defined in ZScale.HighColor:
It's strange (to me) that color this isn't by default the high value of the table, but the option (and LowColor) actually served me well a few times.
10-04-2024 10:36 AM
I don't quite follow. Why would it flip over to "high color" around 232. The correct display of the data would be to show the rest of the shades of blue. Anything else would confuse the user and make them think the value in that right section is over 1000.
10-04-2024 11:10 AM
The bug is with the limit of the Z-scale. The limit should be tied to the plot's numeric representation. The max value of u8 is 255 but the plot is asking for a scale between 0 - 1000. What does 255 out of 100 mean for an integer whose max value is 255?
10-04-2024 11:21 AM - edited 10-04-2024 11:24 AM
On a side note, there was an old bug (introduced in LabVIEW 8 ) with U8 intensity graphs if a marker value is out of U8 range. Not sure if it got fixed.
10-07-2024 02:49 AM
@altenbach wrote:
On a side note, there was an old bug (introduced in LabVIEW 8 ) with U8 intensity graphs if a marker value is out of U8 range. Not sure if it got fixed.
Seems spot on to me.