UPPAALModelChecker / UPPAAL-Meta

This is the offcial meta repo for issue reporting, feature request and public roadmap for the development of UPPAAL.
http://www.uppaal.org
1 stars 0 forks source link

Stratego-8-beta-6: Internal error when opening model where some specific options are saved on query level #17

Closed magoorden closed 2 years ago

magoorden commented 3 years ago

Describe the bug In Stratego-8-beta-6, options other than the default ones can be saved for each query specific. For some of the options, opening such a model result in an internal error "Caught unexpected java.lang.RuntimeException: Could not interpret parameter field properly." At least one of the options resulting in this error is Number of successful runs. At least one of the options resulting in no error is Discretization step for hybrid systems. I don't exhaustively tested all options to figure out which of them result in this internal error.

To Reproduce Steps to reproduce the behavior:

  1. Have a Uppaal model without saved settings.
  2. Select a query.
  3. Click the gear button.
  4. Go to Learning parameters
  5. In the pop-up window, change `Number of successful runs' (the first option) to something else, for example 20 (removing the last 0). A red star should appear behind the option name.
  6. Click OK. Verify that the gear button now has a small yellow circle.
  7. Save the file. You might want to verify that the option has been saved by looking in the xml file for the <option/> tag.
  8. Open another (random) Uppaal model.
  9. Open the Uppaal model with the saved option.
  10. Internal error appears.

Expected behavior No internal error while opening the model. Expected behavior can be observed by following the steps above, but now changing the Discretization step for hybrid systems option.

Uppaal version

Desktop (please complete the following information):

mikucionisaau commented 3 years ago

@waefwerf this seems to be critical as the option settings prevent proper usage.

yrke commented 2 years ago

This issue have been fixed in the latest beta release