Debug Input
This function block writes the content of its input into the log window so you can inspect runtime values. It is useful for quick checks during scenario design and troubleshooting.
π₯ Inputs
Input
Generic data to inspect. If the input is an image, the log will show summary info (min, max, std, size). For other data types the log shows a readable representation.
π€ Outputs
This function block does not produce any outputs.
πΉοΈ Controls
Controls None β this block has no interactive widgets.
π― Features
Simple runtime inspection of any connected data.
Automatic image summarization when receiving image arrays (shows min, max, standard deviation and dimensions).
Lightweight: intended for quick checks and debugging during workflow building.
π Usage Instructions
Connect the data you want to inspect to the
Inputsocket.Run your scenario. The content of the input will be printed into the log window each time the block is evaluated.
Use the log output to verify expected values, data shapes, or to spot unexpected None/empty values.
π Evaluation
When evaluated, this function block reads the current input and posts a descriptive message to the log. Images are summarized; other data types are converted to a readable string before logging.
π‘ Tips and Tricks
Use
Is Nonebefore this block to avoid logging repeated None values and to filter only meaningful data.Pair with
Rising EdgeorLogic Inputto log only on specific events (for example, when a condition becomes true) so the log remains readable.When inspecting image streams, combine with
Show Imageto visually confirm what the image summary refers to.To store inspected values for later analysis, route data to
Data Write LocalorData Write Globaland view them withData Read Local/Data Read Global.If you want to log numeric arrays or tabular data, consider also connecting outputs to
CSV Exportfor persistent logging.Helpful combinations for common checks:
Visual object checks: connect outputs from
Object Detection,Find Object, orMask Detectioninto this block to inspect detection lists and counts.OCR and text checks: feed outputs from
OCRorOCR (EasyOCR)here to verify recognized text before exporting.Image preprocessing debug: place this block after
Blur,Image Threshold, orHSV Filterto inspect intermediate results.
π οΈ Troubleshooting
No log output: ensure the block is connected and the scenario is running. If the input is not evaluated, try adding an upstream trigger (for example
Logic InputorRising Edge).Log shows large unreadable structures: for large images or long lists, use
Show Imageor save data withImage Logger/CSV Exportinstead of relying solely on the log.Repeated identical messages flooding the log: use event gating blocks such as
Rising Edge,All True, or gating logic (And/Or) to reduce how often this block is evaluated.
Last updated
Was this helpful?