![]() |
|
||
|
The Future of MATT Short-term Goals:Currently, we are developing a workhorse class that will serve as a communicator between the MATT GUI and the underlying m-functions that talk to the MATLAB workspace. When this class is completed, all MATT functionality involving Simulink will be detached from the MATT GUI. This will allow us to write multiple GUIs for the MATT program (Windows, Unix/Linux, Mac, etc) and maintain all MATT functionality as separate program entities. Long-term Goals: Next on the MATT agenda is to remove the test types from the MATT engine and place them into MATLAB m-functions. This will allow us easily create new test types for the MATT environment, as well as let users create their own. The template m-function for creating an input test type is this simple: function y = f( x ) Due to MATLABs intrinsic vectorization (ability to perform vector operations without a for-loop), we can easily send vector x to the MATLAB engine, generate input test vector y, and return y to the MATT environment. Finally, our major long-term goal for MATT is to implement the capability to connect to an IP-address and simulate a system externally. In this way, a user will be able to simulate and generate code for external systems, and have neither MATLAB nor Simulink installed on their machine. This idea will take much research and time to implement but the concept is amazing - Such capability would put MATT on the forefront of automated control system testing tools. .
|
|||
|
|
|||
| If you have any questions
or comments, we can be reached at the following addresses: Project Leader: Joel Henry MATT Customer Support Web Support: Spencer Wolny |
|
||
|
|
|||