ImageClear¶
-
MLModule¶ genre FlowControlauthor MeVis Medical Solutions AGpackage MeVisLab/Standarddll MLBasicModulesdefinition mlBasicModules.def see also Bypasskeywords output
Purpose¶
The module ImageClear relays an image with the optional ability to clear the output explicitly or upon input change. This prevents undesired output notifications and potentially undesired updates of subsequent modules.
Usage¶
Put this module in front of a subnetwork where the modules have auto-update enabled to prevent unwanted updates. Put this module after a network with a lot of extra notifications to hide these from the subsequent modules.
Details¶
The input image is not cached but only bypassed, so no performance loss occurs and no memory is used.
Interaction¶
When pressing ‘update’ while the output is already up-to-date, no additional notification is sent. The same goes for ‘clear’ when the output is cleared anyway.
Tips¶
It is often a good idea to implement all input and output image fields of a macro with ImageClear modules (instead of Bypass modules, which do not allow ‘clear’).
Parameter Fields¶
Field Index¶
[]: Trigger |
Clear: Trigger |
Has Valid Input: Bool |
Has Valid Output: Bool |
Update: Trigger |
Update automatically: Bool |
Visible Fields¶
Update automatically¶
-
name:autoUpdate, type:Bool, default:FALSE¶ If enabled, the output image is automatically updated on each input image notification.
Has Valid Input¶
-
name:validInImage, type:Bool, persistent:no¶ Shows whether the current input image is valid.
Has Valid Output¶
-
name:validOutImage, type:Bool, persistent:no¶ Shows whether the current output image is valid.
[]¶
-
name:updateDone, type:Trigger, persistent:no¶ This field is triggered by the module after an update is complete and all output fields are up-to-date and notified.
The field is also triggered if the field
Updateis pressed when the output image is already up-to-date (although the output image andHas Valid Outputfields will not be touched in these cases).