[Question] Remove errors raised by `pyrato.edc.intersection_time_lundeby`

[f-brinkmann]

Checklist

• I searched the documentation.
• I looked through existing discussion topics.
• I looked for similar issues.
• I looked up my question/problem in a search engine.

Question

pyrato.edc.intersection_time_lundeby raises an error if computations fail due to low SNR. This function is called by other functions to truncate and compute EDCs. These functions are commonly used to compute EDCs and later RA parameters in (fractional) octaves. In this case the computation would fail if the SNR is to low in only one band. I think this is unwanted and we should think about other options.

Suggestion:

• pyrato.edc.intersection_time_lundeby returns NaN values instead of raising an error
• pyrato.edc.intersection_time_lundeby could raise a warning instead ans/or we could add an additional return parameter that flags if the computation worked (per channel of the input data)
• Functions calling pyrato.edc.intersection_time_lundeby could return EDCs consisting of only NaN values and/or we could add an additional return parameter that flags if the computation worked (per channel of the input data)

[mberz]

We could also add an option to show a warning instead of raising an error, such as we did with the average function in pyfar.

[f-brinkmann]

We decided to add a parameter to intersection_time_lundeby that makes it possible to raise an error or a warning. The default will be 'error'. All functions that call intersection_time_lundeby will use 'warning' and won't have an additional parameter.

If desired, users have to filter the warning themselves.