Toward visual debugging: integrating algorithm animation capabilities within a source-level debugger
ACM Transactions on Computer-Human Interaction (TOCHI)
Untangling knots by stochastic energy optimization
Proceedings of the 7th conference on Visualization '96
Isosurface extraction using particle systems
VIS '97 Proceedings of the 8th conference on Visualization '97
Visual debugging of visualization software: a case study for particle systems
VIS '99 Proceedings of the conference on Visualization '99: celebrating ten years
Case study: visual debugging of cluster hardware
Proceedings of the conference on Visualization '01
Case study: visual debugging of finite element codes
Proceedings of the conference on Visualization '02
Visualization of Geometric Algorithms
IEEE Transactions on Visualization and Computer Graphics
Visualization of Salt-Induced Stress Perturbations
VIS '04 Proceedings of the conference on Visualization '04
Visualization of Geologic Stress Perturbations Using Mohr Diagrams
IEEE Transactions on Visualization and Computer Graphics
A visual tool for trellis construction and Viterbi decoder of augmented RAC array codes
Proceedings of the 2006 international conference on Wireless communications and mobile computing
Hi-index | 0.00 |
We developed an approach that uses our innate visual pattern recognition skills as part of the debugging process. Inspired by Huang's (1996) use of color to visualize energy distributions while untangling knots, we represented the particles graphically and color-coded them by energy value. Thus far, we've applied this approach to three domains: particle systems, cluster hardware configurations, and physics codes using finite element models. This debugging paradigm differs from software or program visualization in that we don't visualize software elements such as procedures, message passing between processors, or graph-based representations of data structures. In most application domains developers that use algorithm visualization tools must make decisions about what kind of visualization would best represent their code, and they must, in effect, code this visualization in addition to their application. For many developers, the time investment is too great compared to their perceived benefit, so they return to a traditional debugging approach. We believe that restricting the application domain increases the ease of use of visual debuggers. However, we go one step further by creating a, visual tool tailored to a particular application domain that can use either captured data or simulation outputs and requires no coding effort on the part of the user.