Dear all,

I have been waiting for almost a month, could anyone please help me with this question? I really need it

Sincerelym,
Tat Manh Nguyen

To which document are you referring?

Dear Millerjv,

I have attached the file above. I mean slide 4. I was looking for an explanation on the internet but I couldn't find it. could you please explain or send me links to the right information about the External Model Modules, and External Connections?
I need this to explain it in my report.
Sincerely,

Tat Manh Nguyen

I am sorry. But I do not see an attached file. What is the name of the file? Perhaps I can find the original on our wiki.

I suspect that you are looking at an old architecture design. As Slicer is constantly evolving there may be updated documentation that is more relevent. But I can ad IDE better when I see what you are looking at.

Dear Millerjv,

I apologize for my mistake, i forgot to attach the file. Now I have upload it. the name of the file is Slicer 3-beta-2007-04-16 in case you didn't see the file. Thank you for your reply
Sincerely,
Tat Manh Nguyen

Execution Model Modules are plugins. We also refer to them as Command Line Modules. They use an interface modeled after the command line, I.e. argc, argv, where parameters are passed as flags and strings. The modules are discovered automatically at runtime. The modules emit an XML description of their parameters (float, image, table). Slicer then builds a custom user interface for the module. Most parameters are passed directly on the command line. Large bulk data sets are written to disk and a filename is passed on the command line. The modules can be built as either executables or as shared libraries. When built as shared libraries, images can be passed through memory instead of through files.

You can search for Slicer Execution Model Documentation for more information.

There are other plugin module types supported by Slicer. Modules written in python can be discovered at runtime as well. Also Loadable modules are full Slicer modules with unlimited access to Slicer internals that can be discovered at runtime.

All of these module types can be distributed using the Extension Manager which is Slicers App Store.

External Connections is a standard port connection which provides an ability for an external application to send data or pull data from a running instance of Slicer. For instance you can send an image to a running Slicer to display.

Search Slicer Daemon for more information.

There is also OpenIGTLink as a means to communicate with Slicer. This is used mostly in image guided therapy, allowing Slicer to interface with tracking devices and imaging devices.

Thank you very much for your answer.

http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation

http://www.slicer.org/slicerWiki/index.php/Slicer3:Slicer_Daemon

http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.2

http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.2/Developers

If you questions are answered, may I close this bug?

Yes, thank you very much