Skip to content

Files for l1ghtsab3r team #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Files for l1ghtsab3r team #5

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
490eb56
Read for l1ghtsab3r Team added
soummyaah Apr 10, 2016
87a2f6e
Merge branch 'master' of https://github.com/pydsa/pydsa-viz-examples
soummyaah Apr 22, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions l1ghtsab3r/READEME.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
#Team l1ghtsab3r

Soumya Sharma - soummyaah
Srishti Sengupta - SrishtiSengupta


We will be creating a generic frontend/backend framework for visualizing the algorithms. This would remove the overhead burden of having to customize visualizations for each algorithm. The backend server would be written in Flask. The front-end would be managed by generic functions written in d3js. We’ll establish a communication protocol between the server and the front-end JS for passing visualization commands and arbitrary log messages to be displayed. The JS would then plugin to these commands and show the visualizations. This would de-couple the front-end service and backend service and allow us to focus on making them work independently. For instance, for a sorting algorithm, the only visualization command that the frontend should support would be a demonstrateSwap(). Because of this decoupling, the server can demonstrate different sorting algorithms without needing the front-end to be tied to it. Another instance would be to create emphasiseEdge() and emphasiseNode() functions on the front-end. This would allow us to explore different traversals and path finding algorithms without having to worry about clean visualization.