You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When doing multiresolution scale separation it is common for data windows to have a poor condition number. snapshots.Snapshots gives a warning for each window sometimes numbering in the thousands.
Describe the solution you'd like
I would like to add an argument to disable the _check_condition_number step.
Describe alternatives you've considered
Since this poor condition number is to be expected for certain cases such as small decomposition windows, the warnings have to be disabled, which is a suboptimal solution.
Additional context
This would be implemented for the COSTS method in the roadmap. If a different solution is preferred that would have more general utility I would be happy to implement that instead, for instance logging the message at a different level.
The text was updated successfully, but these errors were encountered:
Maybe we can exploit the logging functionalities to address this case.
I would wait for other comments on this, because I am not sure on the best solution.
Is your feature request related to a problem? Please describe.
When doing multiresolution scale separation it is common for data windows to have a poor condition number.
snapshots.Snapshots
gives a warning for each window sometimes numbering in the thousands.Describe the solution you'd like
I would like to add an argument to disable the
_check_condition_number
step.Describe alternatives you've considered
Since this poor condition number is to be expected for certain cases such as small decomposition windows, the warnings have to be disabled, which is a suboptimal solution.
Additional context
This would be implemented for the COSTS method in the roadmap. If a different solution is preferred that would have more general utility I would be happy to implement that instead, for instance logging the message at a different level.
The text was updated successfully, but these errors were encountered: