GIScience / helios

HELIOS - the Heidelberg LiDAR Operations Simulator - is a software package for interactive real-time simulation and visualisation of terrestrial, mobile and airborne laser scan surveys written in Java.
http://www.geog.uni-heidelberg.de/gis/helios.html
GNU General Public License v3.0
87 stars 41 forks source link

set scannerWaveLength #38

Closed dongdada896 closed 4 years ago

dongdada896 commented 4 years ago

Hi, I followed your instruction in helios/FWF.md to set the scannerWaveLength[ns] as 0.000005 in order to make Scanner's operating wavelength become 1550nm. But the console displays that the wavelength is still 1064nm.I don’t know why. Appreciate your help sincerely.

jcsi2410 commented 4 years ago

I have the same question. I've tried editing the survey and scanner xml file but the console still shows 1064nm. Any help would be greatly appreciated?

kathapand commented 4 years ago

Hi! I am not sure about this setting, but you can add it to the instrument specification in the scanner-xml (TLS or ALS). See for example here: https://github.com/GIScience/helios/blob/master/data/scanners_tls.xml#L103

dongdada896 commented 4 years ago

@kathapand I set up according to your instruction and it worked. But there will be a little problem, if you set wavelength_nm = "1550", the console will display Wavelength: 1549nm. All in all, thank you very much for your help.

jcsi2410 commented 4 years ago

@kathapand Thank you for your prompt response. I'd settle for the glitch also mentioned by @dongdada896 image

kathapand commented 4 years ago

Hi! It could be this is a rounding issue, looks like a bug that should be checked. Thanks for documenting the observation! I tried to contact (both/either) of you directly, but cannot obtain contact information. Maybe you could send me a short email (https://github.com/kathapand), then I can write to you. It is an honest inquiry and info on HELIOS, but of course no problem if you prefer not to!

lwiniwar commented 4 years ago

closed as wont-fix (1 nm difference is probably insignificant and may just be a display issue)