The error message produced when providing an invalid averaging value could be clearer

[d3v-null]

This is a placeholder so that I don't forget.

An invalid averaging value was provided through asvo, and the error message just said something like "error parsing cli", but not which specific argument was at fault.

[d3v-null]

This was because the Error types were being printed with

    match result {
        Err(e) => {
            eprintln!("preprocessing error: {e}")
        }
    }

which only showed the error type, and not the detailed error info and line number. now that it's printed with debug "{e:?}", the original error message has been restored.

error parsing args: CLIError(InvalidCommandLineArgument { option: "--avg-time-res <RES>", expected: "a multiple of the integration time, 0.5 [s]", received: "0.1" })

[cjordan]

I think printing the debug representation of the error is not what you want. It might make this particular error look OK, but most other errors will not be human readable (e.g. 35e4cba). This is why it's called a debug rep - it's meant to be for programmers, not humans.

I therefore think that it would be best to change the Display method of the errors you're interested in. Alternatively, you could match on specific errors in your code block above and emit additional details there.

[d3v-null]

I agree that this would be a better solution long term, but I think including the error messages with line numbers provides a substantial improvement over just the name of the error for now. How about I open up a new ticket for this.

[d3v-null]

error looks like this now

error parsing args: Invalid Command Line Argument: option --avg-time-res <RES> expected a multiple of the integration time, 2 [s] but received 0.9999