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 am running jDart on the Raytrace program that have float variables.
jDart outputs "[SEVERE] Coral threw exception" most of the time, leading to a very low branch coverage.
However, from the TACAS2016 paper, jDart achieved a relatively high branch coverage for this program.
I am wondering how jconstraints-coral deals with float relations exactly.
Some limitations of jconstraints-coral are that (Possibly fixed as of coral 0.8),
API allows float and long relations (<, <=, ==, >=, >), but coral 0.7 throws exceptions when they are used
Float and long arithmetic are superfluous (API allows constructing them)
For above reasons, float constants are currently converted to doubles in jConstraints-coral
Do these limitation mean coral will throw exceptions whenever the path condition contains float symbols and jconstraints-coral will fail to solve such path conditions?
If yes, any feasible solutions? Manually convert all the float variables into double variables? Or is it possible to use the latest coral 0.8 here?
Thanks and Regards,
Bihuan
The text was updated successfully, but these errors were encountered:
Hello,
I am running jDart on the Raytrace program that have float variables.
jDart outputs "[SEVERE] Coral threw exception" most of the time, leading to a very low branch coverage.
However, from the TACAS2016 paper, jDart achieved a relatively high branch coverage for this program.
I am wondering how jconstraints-coral deals with float relations exactly.
Some limitations of jconstraints-coral are that (Possibly fixed as of coral 0.8),
Do these limitation mean coral will throw exceptions whenever the path condition contains float symbols and jconstraints-coral will fail to solve such path conditions?
If yes, any feasible solutions? Manually convert all the float variables into double variables? Or is it possible to use the latest coral 0.8 here?
Thanks and Regards,
Bihuan
The text was updated successfully, but these errors were encountered: