# 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 1. Connect the data you want to inspect to the `Input` socket. 2. Run your scenario. The content of the input will be printed into the log window each time the block is evaluated. 3. 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 None` before this block to avoid logging repeated None values and to filter only meaningful data. * Pair with `Rising Edge` or `Logic Input` to log only on specific events (for example, when a condition becomes true) so the log remains readable. * When inspecting image streams, combine with `Show Image` to visually confirm what the image summary refers to. * To store inspected values for later analysis, route data to `Data Write Local` or `Data Write Global` and view them with `Data Read Local` / `Data Read Global`. * If you want to log numeric arrays or tabular data, consider also connecting outputs to `CSV Export` for persistent logging. * Helpful combinations for common checks: * Visual object checks: connect outputs from `Object Detection`, `Find Object`, or `Mask Detection` into this block to inspect detection lists and counts. * OCR and text checks: feed outputs from `OCR` or `OCR (EasyOCR)` here to verify recognized text before exporting. * Image preprocessing debug: place this block after `Blur`, `Image Threshold`, or `HSV Filter` to 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 Input` or `Rising Edge`). * Log shows large unreadable structures: for large images or long lists, use `Show Image` or save data with `Image Logger` / `CSV Export` instead 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.augelab.com/function-blocks/data-logic/referencing/debug-input.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.