Lastools error handling

[dokempf]

No description provided.

[dokempf]

The error is now:

ERROR: LAStools lasground_new (by info@rapidlasso.de) version 251013 (unlicensed)
E           ERROR: license failure. Use '-demo' to run in demo mode.

@han16nah How should we handle this? Should AFWizard switch into demo mode if no license was found?

[han16nah]

The error is now:

ERROR: LAStools lasground_new (by info@rapidlasso.de) version 251013 (unlicensed)
E           ERROR: license failure. Use '-demo' to run in demo mode.

@han16nah How should we handle this? Should AFWizard switch into demo mode if no license was found?

Okay, seems like Linux and Windows behave differently here (Windows seems to automatically switch to -demo) and proceeds the processing, at least the version I tested.

So yes, it should then switch in demo mode. Maybe like:

    if result.returncode != 0 and not "Please note that LAStools is not" in result.stdout.decode():
        raise AFwizardError(f"LASTools error: {result.stdout.decode()}")
    elif result.returncode != 0:
        logger.warning(f"LASTools warning: {result.stdout.decode()}")
        # no license found, switching to demo mode
        args.extend(["-demo"])
        with within_temporary_workspace():
            logger.info(
                f"Executing LASTools command line '{' '.join(executable + args)}'"
            )
            result = subprocess.run(
                executable + args,
                stdout=subprocess.PIPE,
                stderr=subprocess.STDOUT,
            )

I don't know if there is a more elegant way to catch the specific LAStools error..