-
Notifications
You must be signed in to change notification settings - Fork 12
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
Result Visualization #11
Comments
I discovered the file result.fig that I suppose is opened when clicking "Display Result". |
#11 Implement of try catch to get the data from the workspace (sol vector) But the result showing still doesn't work, it is not looking at data in the RaPIdObject
including RaPIdOvject to get the data #11
For first release, the functionality is deemed not yet implemented #11 - Tweaked the code so that it throws a warning message informing user of that.
For Beta 2:
|
Some fixes were added in [1b920ba]
We should think on how to take into account that the output of the fmu is not necessarily what we use for calculating fitness. |
…help * Added a plot to main GUI window and made a start to implementing plotting functionality see ALSETLab#11 - more to be done here * Specifying time step ts now does something useful for Simulink simulations (use ts <=0 to get default behavior) for both fixed and variable step solvers. * Bettered the help text for some m-files
In current version, I haven't been able to use the "Last Result", "Display Result" buttons.
I propose the following implementation:
Additional a message could be printed, telling the user whether the solution could be considered optimal or not. If the optimization has been stopped because of the fitnessStopRatio, the solution can be considered optimal. If the optimization has been stopped because the max number of iteration has been reached, then the solution is not optimal.
The text was updated successfully, but these errors were encountered: