Open mfe7 opened 1 year ago
Thanks for reporting the issue. Here is a workaround by setting bound_opts
when creating a BoundedModule
:
model = BoundedModule(model, nominal_input,
bound_opts={
'sparse_features_alpha': False,
'sparse_spec_alpha': False,
})
Great, just confirmed this works. Thanks for the quick response! I'll leave this open in case there is a root issue to resolve, otherwise feel free to close. Btw, this repo is amazing!!!
Thanks @mfe7 ! There should still be issues to be fixed so it's good to leave this issue open.
Describe the bug For the same model, I can compute output bounds successfully for some choices of epsilon-balls, but receive 2 different errors for some other choices of the epsilon-ball. These errors are appearing when I use
alpha-CROWN
but not when I usebackward
as the method.To Reproduce
Minimum example available in this colab.
The pytorch state_dict file is attached, which can be unzipped then uploaded into the colab file structure. single_pendulum_small_controller.torch.zip
Here's the error I receive when using the input range of
[[1., 1.2], [0., 0.2]]
:Here's the error I receive when I use input range
[[0., 0.2], [0., 0.2]]
:System configuration:
Additional context One thing that is possibly unique/different about this computation graph is that it includes repeated instances of the controller and dynamics to represent the closed-loop system's dynamics across multiple timesteps. I am wondering if there are naming conflicts across timesteps that contribute to these errors.