Table of Contents
Opens an existing MeVisLab network
from file (extension .mlab
).
Alternatively, the .mlab
file can be dragged onto the workspace to open it in a new network window.
Some other file types may also be opened directly by dragging them onto the workspace (no network needs to be open for that):
A dragged image file (.dcm
, .tif
, .png
, etc.) creates an ImageLoad
module that automatically loads the file.
A dragged file readable by WEM modules (.wem
, .off
, .obj
, .ply
, etc.) creates a WEMLoad
module that automatically loads the file. See the HTML help for the WEMLoad
module for more information.
A dragged file readable by CSO modules (.cso
) creates a CSOLoad
module that automatically loads the file.
Saves the current network.
For saved networks, the AutoSave files are discarded. See Section 4.3.1, “Preferences — General” .
Writes the current network to file with a new name.
For saved networks, the AutoSave files are discarded. See Section 4.3.1, “Preferences — General” .
Reverts to the last saved version of the current network. (This option is only available if the network was changed.)
Allows the selecting of a recently opened network from file. The maximum number of recent files is 20. The list of recent files is not deleted upon installing a new version of MeVisLab. For more information about storing preferences, see Section 4.3, “Preferences”.
Opens the most recent network file. This function can be triggered with a keyboard shortcut, see Section 4.3.10, “Preferences — Shortcuts”.
Starts a wizard for creating new modules, packages, and installers (an ADK license is required for the latter). See Chapter 26, Project Wizard.
Creates a new local macro module relative to the current network path, based on the currently selected modules or a module group. See Section 3.11.2, “Editing, Converting, and Deleting Groups”. The necessary inputs and outputs are added automatically. The display names of interface fields can be changed, but their internal names cannot.
Locally defined macro modules can be used in complex networks to encapsulate subnetworks as independent functional units with a defined interface to other network components. In this way, they perform an application-specific function that would not be useful for other applications. Therefore, they are not added to the common MeVisLab module database, meaning they are not declared in a .def
file.
The following items are created:
The files <ModuleName>.script
and
<ModuleName>.mlab
in the current network path directory.
The new local macro module on the current network workspace.
![]() | Note |
---|---|
A local macro module is not available in the MeVisLab module
database, as no To differentiate local macros from global macros, "./" is prepended to the module name/type in the network view to indicate that this module only exists relative to the location of the network file. |
![]() | Note |
---|---|
During the conversion to a local macro, modules must be disconnected and reconnected. Connections set by script, i.e., forwarded from an outer macro, cannot be disconnected, resulting in an alert: “Unable to remove the module [module name] with connections set by script.” A similar alert is issued when attempting to remove a module connected in this way. In the next figure, modules within a red rectangle cannot be deleted, disconnected from inputs/outputs, or added to a local macro. |
For an introduction to macros, read Getting Started, chapter “Introduction to Macro Modules”.
Adds a locally defined macro module to the current network, see Section 4.1.12, “Create Local Macro”. Choose the <ModuleName>.script
file in the file dialog to add the local macro module. The local macro must be defined in the same folder as the network to which it will be added, or in a subfolder of that folder.
Opens MATE with a file dialog where one or more files can be opened, see Chapter 27, MATE.
Opens MATE without files, see Chapter 27, MATE.
Starts the ToolRunner, see the ToolRunner documentation.
Starts the TestCaseManager of the TestCenter, see the TestCenter Reference and the Getting Started, chapter 16, “Using the TestCenter”.
Lists the most recently run test cases from the TestCaseManager. Selecting an entry from this list will open the TestCaseManager and run the selected test case.
This will open the TestCaseManager and run the top-most entry of the recent test cases list.
Restarts MeVisLab with all currently opened networks. This is necessary for a complete DLL update and is useful when developing new ML and Inventor modules. Alternatively, you can press a shortcut to restart MeVisLab with the current network. Refer to Section 4.3.10, “Preferences — Shortcuts”.
![]() | Note |
---|---|
MeVisLab restarts in the same mode in which it was originally started, particularly concerning the |
© 2025 MeVis Medical Solutions AG