CashFlow, A Visualization Framework for 3D Flow - Studierstube ...

Results5.1. Combining MultiData Node & DataAccess Nodeand strategies it is important to keep in mind, that only one constraint for eachRender node has to be satisfied with is:In traversal order the DataConsumer node must be after the correspondingMultiData and DataAccess node.Following that rule we can change the position of the nodes [1]–[6] as long asthey are in front of the Render nodes [7][8][9]. When using absolute addresskeys changing the position of nodes in the scene graph does not influence theresult, since the Render nodes link to the DataAccess nodes directly. This directlinking of nodes is comparable to a field connection and is accomplished viaElements and unique keys used as absolute address keys.Otherwise when using relative address keys the ordering of nodes [1]–[6] effectsthe linking of Render nodes and DataAccess nodes (for details on indirectreferences see section 3.3 on page 43).Figure 5.2: CashFlow Scene Graph Example Render Node reads multiple Input (left): Three MultiData(D),one DataAccess(A) and a Render(R) node. Process flow (right): The Render node [5] requires multipledata input. It is linked via the DataAccess node [4] to the embedded DataAccess map(grey). EachDataAccess map(grey) refers to a separate MultiData nodes [1][2][3]. Note, that the MultiData nodes[1-3] and the DataAccess node [4] may be somewhere else in the scene graph.5. Render node linked to several MultiData nodes: (see figure 5.2)All other examples show one Render node linked to one MultiData node. Thisexample shows a Render node requesting three MultiData nodes. An examplefor such a rendering algorithm is an StreamRibbon Renderer. The first MultiDatanode stores the interpolation points of the streamline, the second node stores theorientation per interpolation point and the third node provides a color–map forthe Ribbon mapped to a scalar value.104