Hi I am lately having hard times with intensity indicators. They seem to be quite buggy. My new discovery is strange working Z autoscale. My understanding of Z axis autoscaling is that it finds maximal and minimal magnitude in data - the minimum is assigned to the lowest element in ZScaleMarker.Values and maximum to the highest one. What is in between is recomputed with uniform step (I mean if there are more ZScaleMarker.Value elements). That's the way how intensity chart works.
But if I turn on autoscale and feed the graph it updates the ramp ticks BUT it doesn't update the ZScaleMarker.Values - is that expected behavior? In addition if I move the VI behind the screen border the ramp changes the color to white - I believe it is because it starts to respect the values in ZScaleMarker.Values (they are still 1-white, 0-black because they aren't refreshed) and thus the actual real values are out of range.
Nevertheless in all cases the data are depicted correctly only the ramp behaves weird.
Could somebody explain this to me?
Just a quick note that may explain what is going on here. Markers actually behave as if they are absolute if you use AutoScale Z. The symptoms of this are what you seem to be describing. I think this may be expected behavoir, but it certainly isn't intuitive. I will take a look to see if R&D has looked at this.
In any case, we should be able to write to the ZScaleMarker.Values property to set it appropriately for our data, just as you have initialized it in your VI.
Good point. I did find reference to Markers being absolute dismissed as expected behavior (for some reason..). Seems like something that would be good to file as a product suggestion. However, your point about the color not updating until the VI finishes execution needs to be addressed. Toward that end, this was reported to R&D (# 124959) for further investigation.