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
I'm trying to verify the given onnx network (both input and output are of size 1) with the given vnnlib property, but I get a spurious counterexample. I use the following terminal command:
After some debugging, I noticed that, when I call the evaluate() method of the NLR object on a specific input, I get the wrong output. For example, if I add the following code snippet after the call to initializeNetworkLevelReasoning() in processInputQuery() in Engine.cpp:
Hi @idan0610 that does indeed sound like there's at least one bug in the C++ parser. I'll try and get some time to look at next week, but in the mean time, any chance you could shrink the network to the minimal example that triggers the bug? As you've already got the debugger up and running, you should be able to work out which layer is causing it fairly easily?
Hello,
I'm trying to verify the given onnx network (both input and output are of size 1) with the given vnnlib property, but I get a spurious counterexample. I use the following terminal command:
Marabou/build/Marabou dp-net_0.onnx dp-net_0.vnnlib
After some debugging, I noticed that, when I call the evaluate() method of the NLR object on a specific input, I get the wrong output. For example, if I add the following code snippet after the call to initializeNetworkLevelReasoning() in processInputQuery() in Engine.cpp:
I get the following print:
input: 1.5; output: 8.37823
But running the given onnx network directly with onnxruntime:
Gives the output 24.654705.
My suspicion is that it is related to the C++ version of the ONNX parser. When I try to load this network in debug mode, I get:
Assertion violation! File /home/idan0610/Marabou_dev/for_elbit_new/Marabou/src/input_parsers/TensorUtils.cpp, line 43
Thanks for your help on this issue!
dp-net_0.zip
The text was updated successfully, but these errors were encountered: