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
When calling storm on any model with a property such as: "P>9223372036854775808/9223372036854775808 [F \"goal\"]" You get the following error:
ERROR (SpiritErrorHandler.h:26): Parsing error at 1:3: expecting <expression>, here:
P>9223372036854775808/9223372036854775808 [F "goal"]
^
ERROR (properties.cpp:54): WrongFormatException: Parsing error at 1:3: expecting <expression>, here:
P>9223372036854775808/9223372036854775808 [F "goal"]
^
Note that the used API function does not have access to model variables. If the property you tried to parse contains model variables, it will not be parsed correctly.
ERROR (storm-cli.cpp:63): An exception caused Storm to terminate. The message of the exception is: WrongFormatException: WrongFormatException: Parsing error at 1:3: expecting <expression>, here:
P>9223372036854775808/9223372036854775808 [F "goal"]
^
Note that the used API function does not have access to model variables. If the property you tried to parse contains model variables, it will not be parsed correctly.
This can for example be obtained using the command: storm -drn storm/resources/examples/testfiles/dtmc/crowds-5-5.drn --prop "P>9223372036854775808/9223372036854775808 [F \"goal\"]"
I would expect either the error to say that a too large number was found or for it to be accepted.
The text was updated successfully, but these errors were encountered:
When calling storm on any model with a property such as:
"P>9223372036854775808/9223372036854775808 [F \"goal\"]"
You get the following error:This can for example be obtained using the command:
storm -drn storm/resources/examples/testfiles/dtmc/crowds-5-5.drn --prop "P>9223372036854775808/9223372036854775808 [F \"goal\"]"
I would expect either the error to say that a too large number was found or for it to be accepted.
The text was updated successfully, but these errors were encountered: