Recent Changes for "States and Animations" - Graph Exploration System (GUESS)http://guess.wikispot.org/States_and_AnimationsRecent Changes of the page "States and Animations" on Graph Exploration System (GUESS).en-us States and Animationshttp://guess.wikispot.org/States_and_Animations2007-08-11 00:22:54EytanAdar <div id="content" class="wikipage content"> Differences for States and Animations<p><strong></strong></p><table> <tr> <td> <span> Deletions are marked with - . </span> </td> <td> <span> Additions are marked with +. </span> </td> </tr> <tr> <td> Line 1: </td> <td> Line 1: </td> </tr> <tr> <td> </td> <td> <span>+ = States and Animations =<br> + Graphs are frequently dynamic objects where node and edge properties are changing. In order to support graphs of this nature, GUESS allows users to save and load states of the graph where nodes and edges can appear and disappear and where properties can change in value.<br> + <br> + <br> + <br> + The commands for doing this are simple. Simply type:<br> + <br> + <br> + <br> + * ss(name) to save a state named “name” and<br> + * ls(name) to load a state named “name”<br> + <br> + <br> + All node and edge features will be updated to reflect the new state.<br> + <br> + <br> + <br> + In order to visualize transitions between different states, GUESS provides a morph command that will smoothly change nodes and edges from various states. Simply type morph(statename,time) and the graph will change from the current configuration to state statename over the time milliseconds.<br> + <br> + <br> + <br> + In combination with the movie output features one could save a movie of a morph by doing:<br> + <br> + <br> + {{{<br> + ss(“foo”)<br> + <br> + … do some stuff…<br> + <br> + ss(“bar”)<br> + <br> + startMovie(20,”out.mov”)<br> + <br> + morph(“foo”,50000)<br> + <br> + stopMovie()<br> + }}}<br> + <br> + <br> + We suggest the use a long morph time for smooth animations. Again recall that the output will not be in real time. A 50 second animation may only output a 3 second movie depending on the number of nodes, edges, and processing time.<br> + <br> + <br> + <br> + Nodes and edges move in and out of visibility by adjusting their transparency and they will gradually fade or appear from the background. You may also notice that they disappear too late or appear too early and clutter the display. GUESS allows you control this through a few methods:<br> + <br> + Morpher.setNodeDisappearBy(n) and Morpher.setEdgeDisappearBy(n) will control the disappearance of nodes and edges. The value of n should be between 0 and 1 (1 is the default, so graph elements stick around until the very end). If we wanted them to instantly disappear we would use a value of 0. We find that somewhere around .2 works well (i.e. elements vanish quickly but are still on the screen).<br> + Morpher.setNodeAppearAfter(n) and Morpher.setEdgeAppearAfter(n) will control the appearance of nodes and edges. The value of n should be between 0 and 1 (0 is the default here). We find that somewhere around .8 works well.<br> + <br> + [camera tracking, multi-state morphs]</span> </td> </tr> </table> </div>