Commands crashing with no error

[Glen Shennan]

Hi,

Using laslook I've had a few commands crash, mostly lasthin64, sometimes lasground_new64, presumably due to system resources being exhausted (1.4 billion points). The problem is that there's little or no indication that the command has failed and nothing is running. It seems the terminal goes green, but that happens sometimes anyway, and the progress bar disappears, but when you've got a command that's been running for half an hour and I'm just glancing at the output it can be really hard to notice that something's gone wrong. Indeed, for new users, or just users who haven't encountered this problem before, there's really no indication that anything has gone wrong at all. It would be great to have some kind of output indicating that the command has stopped without reaching the end of processing.

Regards,

Glen Shennan

[Jochen Rapidlasso]

Hi Glen,

thanks for the hint. The process handling in laslook is not perfect right now. It was intended to use laslook to test files and workflows with small files. To scale and to go to production it is better to use a batch or python script to run the commands.

Processing 1.4 billion files in any case will be not too much fun. It is absolute recommended to do a tiling to files around 20 million points: This should run much smoother and faster - and optionally in multi core.

Anyway, we will improve laslook to handle such large files better.

Best,

Jochen @rapidlasso

[Glen Shennan]

Hi Jochen,

Thanks for your response. I both work in research and am a relative beginner with LasTools so virtually all of my work right now is testing workflows.

Thanks for the hint with lastile, I had suspected something like that might be the case. I've been checking the running processes to see when/if the command stops but without an error message it is hard to tell what's happening.

Regards,

Glen