01-16-2022 04:59 AM
I'm able to plot the data. The curve of the distribution is very nice. But the scale of Y axis is difficult for the audience to understand the meaning of the data. In order to make it easier for the audience. I would like to change Y axis to the one shown in the desired Y axis scale. Could anyone share some ideas with me?
1. My VI:
2. Probability plot done by my VI:
3. The desired Y axis scale:
01-16-2022 09:16 AM
It is fine to attach pictures to show the effect you want, but please attach actual VIs (not pictures of part of a Block Diagram) for the following reasons:
In your case, you should also attach an appropriate Data set so we can see how well our suggestions meet your needs.
Here is a thought (for free, without eyestrain):
LabVIEW has two kinds of scales for axes -- linear and logarithmic. In a logarithmic scale, numbers are "spread apart" at small values, and get "bunched together" as they get larger (i.e. the space between 0.1 and 1 is the same as the space between 1 and 10, and between 10 and 100). In your Graph, the spacing goes in the opposite direction. This makes me think that the Y axis should be plotting something like log(1/x) -- too bad I don't have your code to test this hypothesis ...
Bob Schor
01-16-2022 12:40 PM - edited 01-16-2022 01:42 PM
See here (this is for a linear x-axis. I am sure you can adapt to your scenario)
(Note that the crossed out advice only works for linear and logarithmic, so won't apply here)
Also:
@DavidWei wrote:
1. My VI:
As has been said already, diagram pictures are pretty useless (with some exceptions :D). All we can see is that you are doing things in an extremely convoluted and inefficient way. "delete from array" NEVER belongs in a tight loop. All you need is a FOR loop with a conditional output tunnel! NONE of your shift registers are needed. The pink can be replaced with autoindexing at the output tunnel and the brown one with conditional indexing (Guessing, because we cannot see what's in the other case!).Not sure why you "not" the "Include" button instead of just swapping the cases? Do you really expect the user to potentially change that button during the nanoseconds the loop executes, with completely unpredictable results? If not, the terminal belongs before the loop and other things could be simplified.
01-16-2022 07:58 PM
Thanks for your quick response and suggestions.
here attached is my VI.