NoDataAlert¶
Alert if no data is present.
Checks that data is coming through the pipeline, and gives a user alert using a popup window or log message in cases where either no data (Packets are either None or contain no data), has come through for a configurable amount of time. Verbose mode also writes a log message once per second indicating whether data is being received or not. A 'no-data' or 'data-ok' message is sent once per second to the notifs output port in the form of a marker stream (which could be, for example, connected to an LSLOutput node to notify a remote application). Version 1.1.1
Ports/Properties¶
data¶
Data to process.
notifs¶
Notifications/alerts as markers in a marker stream
allowed_gap¶
Amount of time, in seconds, for which there can be no data before an alert is sounded (at any time when the pipeline is running). Set both this param and markers_allowed_gap to 0 to skip checking for data.
allowed_startup_delay¶
Time, in seconds, by which to delay starting to check for no data when the pipeline is first launched (ie., to give the device time to connect, or start an LSL stream, etc.)
markers_allowed_gap¶
Specify a separate allowed interval for any marker streams (since they may emit data at greater intervals). Setting this to 0 will not check any marker streams for data.
exclude_streams¶
A list of streams to exclude from the data check. Leaving this empty (None) will sound the alert if any stream in the data packet does not have data for the specified period of time.
popup_window¶
Pop up a notification window when no data is found after the number of seconds in the allowed_gap parameter. When set to false a message is printed to the log stream only.
verbose¶
Print a log message once a second indicating whether data is being received or not (after the startup delay). If false, log messages are only printed if data is not being received.
notif_frequency¶
Frequency, in seconds, at which to send notifications and print log messages.
set_breakpoint¶
Set a breakpoint on this node. If this is enabled, your debugger (if one is attached) will trigger a breakpoint.
metadata¶
User-definable meta-data associated with the node. Usually reserved for technical purposes.