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

Results5.1. Combining MultiData Node & DataAccess NodeFigure 5.3: Simple CashFlow Scene Graph Example (left): One MultiData(D), one DataAccess(A) and aRender(R) node. The root node is a Separator (S). Process flow (right): Each Render node [3][4][5] usesits own DataAccess map(grey) inside one DataAccess node [2] referring to one MultiData node [1]. Figure5.1 shows a possible result of this scene graph were each Render node generates one of the three grids.Figure 5.4: CashFlow Scene Graph Example with several DataAccess nodes (left): Three MultiData(D),one DataAccess(A) and a Render(R) node. Process flow (right): Each Render node [5][6][7] uses its ownDataAccess map(grey) inside one DataAccess node [4] referring to several MultiData nodes [1][2][3].This scene graph may produce the same output as scene graph from figure 5.3.Figure 5.5: CashFlow Scene Graph Example with several MultiData nodes (left): One MultiData(D), threeDataAccess(A) and a Render(R) node. Process flow (right): Each Render node [5][6][7] links to aseparate DataAccess node [2][3][4] and accesses the DataAccess map(grey) inside. All DataAccess map’s(grey) refer to the same MultiData nodes [1]. Although this process flow differs from figure 5.3 andfigure 5.4 the visual result may stay the same.Figure 5.6: CashFlow Scene Graph Example with several MultiData nodes (left): Three MultiData(D),three DataAccess(A) and a Render(R) node. Process flow (right): Each Render node [7][8][9] is bound toa separate DataAccess node [4][5][6] using the embedded DataAccess map(grey). Each DataAccessmap(grey) refers to a separate MultiData nodes [1][2][3]. Although the four introduced scene graphs lookquite different, they may produce the same visual results, because of the DataAccess node interface.105