Lukas Winiwarter

Hi @Hannes9, glad to hear we are making progress! 1. I think we should talk a bit about your expectations of the output before we see what parameters we can...

Hi @Hannes9, I just double checked the results from yesterday and the 10 second survey results in 12 Mio. points. This corresponds to a total pulse repetition frequency of 1.2...

Hi @Hannes9, thanks for clarifying. The HELIOS++ XYZ output contains coordinates, intensity, and GPS time with a significant amount of digits after the comma, and some additional information. As I...

Hi again @Hannes9 , the datasheet says that it _generates_ 640,000 pts/second for a single one of the sensors. HELIOS++ expects you to provide a value valid for a single...

Hi @Hannes9 , It's probably not documented well. Multi-channel sensors are still quite new in Helios++ and the dev team typically works with other sensors in their research, which is...

Hi @Hannes9 , No, it's not possible to predict the runtime for a simulation apart from very rough heuristics. Re: the second option: When you start the simulation, there is...

Hi @Hannes9 , sure: say you start a survey at 10:02:00 am computer time. It runs until 10:04:20, so a total time of 2 mins and 20 seconds. This is...

Hi @Hannes9, if you want to know the position of the platform (the trajectory) for when a specific point was recorded, you take the GPS Time of that point, find...