[Image Processing Engineer Column] Inference and Speculation
アポロ精工 アポロ精工 新横浜オフィス（旧ケーアイテクノロジー/旧市川ソフトラボラトリー）
Please check the differences in words in a dictionary. Since this is an engineer's column, I will consider the "dangers of speculation" and the "hypotheses" for making assumptions. This theme applies in various scenes, from specification decisions to debugging. To avoid divergence, I will focus on the "debugging scene." In image processing development, even if there is a lot of noise or the image is distorted, once you can obtain an "image (a collection of two-dimensional array data)," you can speculate about issues from a visual perspective. A common pitfall of speculation is the behavior of trying various things in trial and error, thinking, "Could this be the problem?" For whatever you try, if the result is A, consider that a "hypothesis," and if the result is B, treat that as another "hypothesis," also forming a hypothesis for the cause of each result obtained. You should not continue testing until you can organize these. If it becomes a habit to test without considering hypotheses, escaping that quagmire will rely on luck. As you gain experience, it becomes more common for trial and error to accidentally lead to fixing issues. This is the "danger." Since humans think and design, mistakes can occur, necessitating debugging. *News is distributed through our company's newsletter.
Related product information
