- Allowing the access to Matlab variables that are defined in a Matlab module once that module terminates, as if that code was run in the Matlab command line environment.
- Offer a more user-friendly interface to send matlab commands and display the results. Right now the way to do it is to go in MatlabCommander and to type the command in a LineEdit, after which the output result appears in another LineEdit. While it is functional, our end users have had difficulties handling it since the display isn't as nice as in a Matlab console.
- Offer a way to visualize the Matlab workspace variables just like in the Matlab environment: there is currently no way in MatlabBridge to see the variables of the current instance.
|
- Discuss with Andras to better understand the way MatlabBridge work, and showcase an example where we can not access the variables defined in a Matlab module once it has ended. This will lead to a work allowing to address the first objective.
- Look into using a custom ctkConsole (like the python console) in order to mimic the console from the main Matlab environment, OR try to get the commandwindow command from Matlab to directly open up.
- Retrieve workspace from the Matlab instance after each command sent (or matlab module run) and display the variables and their values in a table node, OR try to get the workspace command from Matlab to directly open up.
|
|
