• No results found

Sara Florian

N/A
N/A
Protected

Academic year: 2021

Share "Sara Florian"

Copied!
27
0
0

Loading.... (view fulltext now)

Full text

(1)

Sara Florian

2009-11730

(2)

 What is Plan Visualization?  Why it is needed?

 How it is going to be implemented?  Workflow

 Time line?

 Time line Overview  Program Structure  Conclusion

(3)

3D visualization of plan trees.

Plan trees are query evaluation plans of SQL

queries which are build by the Data Base

Management System(DBMS)

(4)

As the quantity of information that is being managed

by DBMS increase it is harder to clearly show the tree.

Too much information which is not understood easily

loses its value.

The information being shown should be clearly

organized and easily understood by the user.

Why 3D?

Will a 3D implementation of PlanViz be more efficient

and clear to understand than the already existing 2D

implementation?

(5)

As a Web page which can be accessed form smart

pads but also computer.

Create a tree timeline showing its node’s real

execution time while abiding to the tree hierarchy.

Tools:

◦ HTML5:  User interaction ◦ Javascript:  Graphics:  Three.js-3D library

(6)

Connect Server

Log in

Select/Add Plan Tree

Show 3D Plan Tree

Manipulate Plan Tree:

◦Rotation

◦Translation

◦Change between Timeline

view mode and Normal view mode:

PC: <ctrl>+left click Tablet: 3 fingers

(7)

 Visualization of time information for each node in a

chronological way.

 Can help to understand the different events that the node

executes at determined moment and the interaction between them.

 Will it provide a better understanding of the tree execution

and its node interactions?

 Functionality:

 Show the three node’s characters: open, fetch and close

time.

(8)

Time Axis

Plan Tree Time Characters

(9)

 Features:

◦ OBEJCTS:

 Time Axis

 Time(ms)  Guide lines

 Plan Tree: side view

 Name

 Total cost (%)

 Time Characters

 Open, Close and several Fetch.

 Context Menu:

 Color code <zoom out view with rotation>

 Zooming Controls  Restore Control

◦ User Interactions:

 Rotation  Translation

 Zooming In and Out: Use buttons in context menu

(10)

Features:

◦ User Interactions:  Translation  Plan Tree:  Vertical movement  Time Axis:  Horizontal movement  Time Characters:  Vertical

movement-follows Plan Tree vertical translation

 Horizontal

movement-follows Time Axis horizontal translation

◦ Allows to explore plan trees that don’t fit the screen

<Plan tree translation>

(11)

Parsing

Json Creation RendererTree.js InteractionsTouch Touch Input SQL (.plv file) Load Json Plan

(12)

Thought 3D plan tree visualization is more

appealing in a visual way its performance is

similar to the 2D PlanViz.

3D drawings expressed in 2D way will always

have drawbacks:

◦ Side view of timeline shows the leftmost nodes so other children nodes are only visible if timeline is rotated.

◦ Even when timeline is rotated is difficult to visualize in chronological order the character nodes and understand which occurs first than others when comparing several characters.

Real 3D visualization might be more useful but

(13)

 Current view:

◦ Time Axis

◦ Tree Side View

◦ Node Projections

◦ Guidelines  Data:

◦ Randomly generated

 Problem:

◦ Guidelines are not enough to

show clearly the node’s time.  Touch/Mouse Interactions:

◦ Rotation

◦ Translation

(14)

 Current View:

◦ Addition of Grids

 Data:

◦ Randomly generated

 Problem:

◦ Lost of tree and timeline when exploring projections

 Touch/Mouse

Interactions:

◦ Rotation

◦ Translation

(15)

 Problem:

◦ Tree and time axis get out of focus when exploring timeline.  Solution:

◦ Touch/Mouse interaction for each element(tree, timeline, and projection).

◦ Rotation is done by all the elements together . ◦ Translation:  Plan Tree:  Vertical movement  Timeline:  Horizontal Movement  Node projections:

 Horizontal movement: in relation to

timeline

 Vertical movement: in relation to

(16)

 Problem:

◦ Interaction between normal plan

tree view and timeline

 Solution:

◦ Creation of TimeLine mode and

Normal mode

◦ Touch/Mouse Interaction to

enable/disable TimeLine mode:

 <ctr+left click>

 Touch with 3 fingers

 Pseudocode:

◦ If(TimelineMode==true)

◦ Main tree rotated 90°

◦ Node projection enable

◦ Exploration in Y/Z axis enable

◦ Time axis y position

(17)

 Problem:

◦ Tree and time axis get out of focus when exploring timeline  Solution:

◦ Creation of TimeLine mode

 Pseudocode:

◦ If(TimelineMode==true)

◦ Main tree rotated 90°

◦ Node projection enable

◦ Rotation allowed (rotate together)

◦ Exploration in Y/Z axis enable

◦ Timeline position fixed – always in screen

◦ Main tree position fixed – always in screen

(18)
(19)

 Data:

◦ User real data

 Touch/Mouse Interactions:

◦ Rotation: all objects

◦ Translation:

 Plan Tree: Vertical  Time Axis: Horizontal

 Projections: Vertical and Horizontal  Problem:

◦ Time scale too large

◦ Difficulty navigating the time line

◦ How to differentiate the 3 type of time characters

 Solution:

◦ Overview of timeline

◦ Color code border for different character  Yellow-Open

 Blue- Fetch  Red-Close

(20)

Problem:

Are time characters

being draw correctly?

Solution:

(21)

 Problem: ◦ Position of node’s characters in relation to other characters. ◦ Correct position of guidelines  Solution:

◦ Correct code to ensure correct position of

projections and guidelines:

 .js files responsible of

drawing the projections and guidelines. (timeline.js and cubeprojection.js)

(22)

Problem:

Plan trees with

hundred fetch

characters

Guidelines of fetch

characters creates a

plane-like structure

Solution:

Draw guideline only

(23)

Problem:

◦ Time displayed

incorrectly

◦ Close character

guideline position is off

◦ 

Solution:

◦ Correct mismatching code in guideline.js to match cubeprojection.js

◦ Add code to ensure

correct time display for different time scales

(24)

Problem:

◦ Fetch slows down

rendering time

◦ Projection does not

start at 0

Solution:

◦ Group all fetch and

create only one fetch character

◦ Correct code for

projection

positioning(cubeproject ion.js)

(25)

Problem:

Overview of timeline

can make it difficult

to see some

characters or/and

guidelines clearly.

Solution:

Zooming controls:

 Buttons enabled only

(26)

Problem:

No user guide

Solution:

Context Menu:

 Color guide  Zooming Controls

(27)

.htlm Touch.js PlanRenderer.js Renderer.js PlanTree.js Node.js Link.js TimeAxis.js TimeLine.js TimeBars.js CubeTime.js CubeProjection.js

References

Related documents

One approach that we viewed as a distinct family of business models is to build on the traditional utility business model involving conventional cost of service regulation, but

Approach: (1) establish a network of industrial partners, (2) field exposure of 27 products, (3) develop lab method, (4) validate method with inter-laboratory study, (5) develop

Interlanguage studies soared in the 1970s and were mostly involved with learners' linguistic competence, but emphasis on communicative competence and especially

Results shows that jackfruit peel as a potential source of natural cellulose has been comparing favourably with commercial grade cellulose used for food and

There is, moreover, a further discrimination to be made between these two religions.. Heliopolis was a Lower Egyptian religion, whereas the Osiris-cult of. Abydos

Nanog+ Colonies from Neural Stem Cell and Astrocyte Reprogramming Can Emerge Independent of E-Cadherin or SSEA1.. (A) Immunofluorescence (IF) images of NANOG colonies on day 10

V této kapitole budou navrženy změny vedoucí k eliminaci nedostatků stávajícího systému hodnocení dodavatelů, které byly zjištěny v kapitole předchozí. Budou