From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
03-28-2022 10:06 PM
Here is my problem. If I first load a 20x20 array of doubles into my intensity graph, this array takes up the entire field of view. If I later load a smaller 10x10 array, only a quarter of the field is occupied as shown below. Conversely, if I load a larger array, not all of the contents are displayed
Is there any way that I can rescale this graph (for lack of a better term) to work with inputs of different sizes?
Solved! Go to Solution.
03-28-2022 10:30 PM
Set the x an y axis to autoscale.
03-28-2022 10:40 PM - edited 03-28-2022 10:44 PM
I tried setting XScale.ScaleFit and YScale.ScaleFit to 2. I also verified that autoscale is set on both axes. That didn't do the trick.
03-28-2022 11:10 PM
Please attach a simplified version of your vi. Preferably LabVIEW 2020 or older.
03-29-2022 10:40 AM
Here is a simplified VI, as requested. If you click on the toggle, you can see that one of the images occupies the entire graph, whereas the smaller one doesn't. This creates a problem for us when we attempt to load images of different sizes.
Any suggestions for how to approach this? I tried a bunch of properties in the intensity graph, but none of them did the trick.
03-29-2022 10:51 AM - edited 03-29-2022 10:56 AM
Turn off "loose fit" for both axes or change the axis formatting to show at least two decimal digits.
(With loose fit enabled, it will round to the nearest "nice" value for the limits, which is tricky with a 0.05 increment and markers limited to zero digit precision, i.e. whole numbers.)
03-30-2022 10:47 PM
That did the trick. Thanks. I do have a problem with the x- and y-axes, but that's a separate issue that I'll raise later. Again, thanks.