Quantcast
Channel: Machine Vision topics
Viewing all articles
Browse latest Browse all 1272

DispayMapping16 bit in LabVIEW NXG

$
0
0

Dear colleagues,

 

not sure if this question shall be placed in LabVIEW NXG thread or in Vision, let start here.

 

Using DisplayMapping16Bit property I've got pretty strange result. For example, for  the gradient 0...65535 I mapping the image to 10000...20000 range:

 

code nxg Screenshot 2019-01-17 18.31.41.pngLabVIEW NXG 3.0 code

and here is the result from LabVIEW NXG:

 

nxg result - Screenshot 2019-01-17 18.32.11.png

But expected result is the following:

expected Screenshot 2019-01-17 18.32.56.png

checked with LabVIEW 2018 / VDM 2018

code lv2018 - Screenshot 2019-01-17 18.33.42.png

 

Could be a bug in assumption that the conversion method should work in the same way in both Development Environments. Anyway I was unable to get the same result with different conversion methods.LabVIEW NXG Project in attachment.

 

Any idea?


Viewing all articles
Browse latest Browse all 1272

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>