Difference between revisions of "2013 Project Week:CliMatlabInterface"
From NAMIC Wiki
| Line 34: | Line 34: | ||
* a very simple cli module that utilizes openigtlink to send over a simple matlab script and receive the result from matlab server is implemented. | * a very simple cli module that utilizes openigtlink to send over a simple matlab script and receive the result from matlab server is implemented. | ||
* A matlab server script that can communicate with cli module using openigtlink protocol is implemented and it is native to matlab so no need to compile mex files. | * A matlab server script that can communicate with cli module using openigtlink protocol is implemented and it is native to matlab so no need to compile mex files. | ||
| + | * a simple matlab script that does not involve slicer inputs and outputs can be run currently. | ||
</div> | </div> | ||
Revision as of 19:35, 10 January 2013
Home < 2013 Project Week:CliMatlabInterface
CLI module utilizing openigtlink to connect matlab server to run a matlab script.
Key Investigators
- PMH, Toronto: Kevin Wang
- Isomics: Steve Pieper
- Queen's: Andras Lasso, Csaba Pinter
Objective
The goal is to discuss the possibilities and the best course of action for the CLI Matlab interface.
Approach, Plan
- The current approach is described in the corresponding SlicerRT ticket.
- Basically a cli module is used to set up an openigtlink to a matlab server. then the matlab script and any inputs and outputs are transferred using openigtlink.
Progress
- a very simple cli module that utilizes openigtlink to send over a simple matlab script and receive the result from matlab server is implemented.
- A matlab server script that can communicate with cli module using openigtlink protocol is implemented and it is native to matlab so no need to compile mex files.
- a simple matlab script that does not involve slicer inputs and outputs can be run currently.
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as changes in the Slicer4 core
