-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assert not sparse_intermediate_bounds or use_sparse_conv is False #49
Comments
@yusiyoh Maybe could you please try also setting I am not able to run the notebook for now -- it's showing
BoundedTensor annotates the original image with a perturbation. If it's an Linf perturbation, then there will be a lower bound and an upper bound for the perturbed image. Not sure what kind of visualization you are looking for? |
Sorry for inconvenience. This version should be okay: https://colab.research.google.com/drive/1b4PMeK0NKmeXV-mKCfeopbuoJYHa8W4S?usp=sharing Changing
So can I select an arbitrarily perturbed image between the lower and upper bound as a sample from the perturbation set? Or how can I visualize this perturbation set in general? I am not sure if my question makes sense, but I am trying to have a sample from the perturbation set and forward it to the model to get the corresponding prediction. |
Hello and thank you for this amazing tool!
I have also tried to use alpha-beta-CROWN with the same setup but had the same error in the title.
You can find the issue here: Verified-Intelligence/alpha-beta-CROWN#28
With auto_LiRPA, CROWN works as expected but when I change to alpha-CROWN, I have the following error:
My implementation is here: https://colab.research.google.com/drive/1b4PMeK0NKmeXV-mKCfeopbuoJYHa8W4S?usp=sharing
Weights and data:
model_data.zip
I do not get the cause of the error. I tried 'sparse_features_alpha': False, 'sparse_spec_alpha': False but got same results.
Another point is: How to visualize the perturbed image? How does BoundedTensor change the original image?
Thanks in advance and best regards
The text was updated successfully, but these errors were encountered: