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
In #528 we added the option set_operations with default value "lazy". If set_operations is "zonotope", it uses concrete operations between zonotopes, and needs to convert to zonotope. Sets such as Ball2 is not allowed.
Proposal: if convert(Zonotope, X0) is not available, call overapproximate(X0, Zonotope) or (if it is not defined), just convert(Zonotope, overapproximate(X0, Hyperrectangle)).
The text was updated successfully, but these errors were encountered:
I changed my mind here.
It does not make sense to use zonotopes if the sets in the input are not given as zonotopic sets. Since there is (probably) no generic overapproximation method for zonotopes, unexpected things can happen.
I would say that the user should take care of the conversion in advance. Hence I would say that we can keep the existing converts.
In #528 we added the option
set_operations
with default value"lazy"
. Ifset_operations
is"zonotope"
, it uses concrete operations between zonotopes, and needs to convert to zonotope. Sets such asBall2
is not allowed.Proposal: if
convert(Zonotope, X0)
is not available, calloverapproximate(X0, Zonotope)
or (if it is not defined), justconvert(Zonotope, overapproximate(X0, Hyperrectangle))
.The text was updated successfully, but these errors were encountered: