LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Executing "bring to center" on a free cursor in a log XY graph brings the cursor to the top rim of the graph (instead of the center)

Solved!
Go to solution

Dear support,

dear LV users,

selecting "bring to center" for a free cursor in a XY graph does not
bring the cursor into the center of the graph, but instead the command brings it to the
mean/average value. This is not an issue for a linear mapping
of the axis [due to the fact that the center of the axis is equal to
the middle/average value of the end points on the axis]. But when
mapping of the axis is logarithmic, the cursor ends up on the top of
the screen. That is because the average value of the end points
(min(y_axis)+max(y_axis))/2) is not equal to the center of the axis.

Is that a wished behavior, please?

Example: For an y_axis = [1..100], the awaited center position would be at
10 and not at 50.5. The center position for the logarithmic mapping
should be calculated as (log(min(y_axis))+log(max(y_axis)))/2, IMHO.

Kind regards,

0 Kudos
Message 1 of 15
(4,531 Views)

Hello,

 

which version of LabVIEW do you use?

 

Richard

0 Kudos
Message 2 of 15
(4,492 Views)
I am using LV 2013.01f please
0 Kudos
Message 3 of 15
(4,481 Views)

You are right, LabVIEW chooses this form (min(y_axis)+max(y_axis))/2).

 

You can go to "idea exchange".

Link:

http://forums.ni.com/t5/ideas/v2/ideaexchangepage/blog-id/labviewideas

 

here you can see how many people like your idea.

Perhaps it will be considered in the next version of LabVIEW.

0 Kudos
Message 4 of 15
(4,471 Views)

Richard,

 

Please check with R&D to see if they consider this a bug. While it is the built-in behavior, it clearly is meaningless, if not wrong, for the logarithmic mapping option.  If they classify it as a bug, then it does not need to go to the idea exchange.

 

Lynn

0 Kudos
Message 5 of 15
(4,459 Views)
Solution
Accepted by topic author ghighuphu

Lynn,

 

it is definitly no bug. You can make a feature request.

I cannot escalate this case. LabVIEW wants this behaviour.

 

Perhaps it is possible to programm a work around with a property node.

 

Richard

0 Kudos
Message 6 of 15
(4,447 Views)

Dear Richard, dear Lynn

 

thank you for thinking about the issue.

 

What do you mean by "LabVIEW wants this behavior"?

 

Working with a property node is not really a useful workaround: the cursor is going to be updated only when the VI is running. I am working with the cursor only when debugging, that means the VI is mostly stopped, o running step-by-step.

 

OK, I'll post it as a feature request.

 

Cheers,

0 Kudos
Message 7 of 15
(4,438 Views)
Correction: the center on a log-axis is calculated differently:
y_visualCenter = 10^(log(min(y_axis))+log(max(y_axis)))/2
0 Kudos
Message 8 of 15
(4,430 Views)

"LabVIEW wants this behaviour" means that the developer of NI programmed this function like this.

Sorry for my imprecise answer.

 

0 Kudos
Message 10 of 15
(4,420 Views)