Skip to content

GSoC Ideas 2018

Jump to bottom
Richard Müller edited this page Jan 22, 2018 · 39 revisions

General

This documents provides an overview over ideas for projects from Google Summer of Code 2018. Every idea consists of a list of keywords representing the technologies you are most likely will get in touch with during the project. This does not mean you already have to be familiar with them, preconditions are listed separately. Getaviz is a very heterogenous project, containing different components which uses completely different technologies. The keywords will help you to find a project you are interested in, so you can work with the technologies you are enthousiastic about! Further, the focus of most projects can be shifted a bit according to your interests. Just talk to us! The following list gives you an overview which technologies we use in Getaviz:

Programming languages

Visualization frameworks

Hardware

Databases

Ideas

Generator

JavaScript Parser

  • Brief explenation
  • Expected results
  • Involved Technologies
    JavaScript
  • Knowledge Prerequisite
    You should already have some experience with JavaScript. With this task you can deepen your knowledgte and get in touch with almost every aspect of the language, even the unpopular ones.
  • Mentor
    David Baum [david.baum(at)uni-leipzig.de]

Unity Output

  • Brief explanation
    Currently, 2D and 3D visualizations are generated in x3d and x3dom. Unfortunately they don't support HTC Vive. In contrast, unity supports this very well. To better support virtual and augmented reality, the generator should be capable of generating Unity as additional output format. We will try to provide you with a HTC Vice so you can test your implementation adequate. Further, it should be possibe to navigate within the VR model and interact with it. Finding suitable interaction and navigation concepts is a highly creative challenge where you can bring in your own ideas!

  • Expected results

    • Every currently supported visualization metaphor can be generated in Unity
    • Implementation of a basic interaction and navigation concept using HTC Vive controlers

  • Involved Technologies
    Java, Xtend, Xtext, Unity, HTC Vive

  • Knowledge Prerequisite
    Experience with at least one high-level language, e.g. Java or C++. Experience with Unity is desirable, but not necessary.

  • Mentor
    David Baum [david.baum(at)uni-leipzig.de]

A-Frame Output

  • Brief explanation
    Currently, 2D and 3D visualizations are generated in x3d and x3dom. Unfortunately they don't support HTC Vive. In contrast, Mozillas A-Frame supports this very well. To better support virtual and augmented reality, the generator should be capable of generating Unity as additional output format. We will try to provide you with a HTC Vice so you can test your implementation adequate. Further, it should be possibe to navigate within the VR model and interact with it. Finding suitable interaction and navigation concepts is a highly creative challenge where you can bring in your own ideas!

  • Expected results

    • Every currently supported visualization metaphor can be generated in A-Frame
    • Implementation of a basic interaction and navigation concept using HTC Vive controlers

  • Involved Technologies
    Java, Xtend, Xtext, A-Frame, HTC Vive

  • Knowledge Prerequisite
    Experience with at least one high-level language, e.g. Java or C++. Experience with A-Frame is not necessary.

  • Mentor
    David Baum [david.baum(at)uni-leipzig.de]

Porting to d3

  • Brief explanation
    Currently, 2D and 3D visualizations are generated in x3d and x3dom. The user interface expects x3dom and cannot interact with other visualization framework. To better support user interaction and dynamic layouts, the generator should be capable of generating d3 as additional output format. It might be useful to use react components for this to increase reuse, but this needs further evaluation. Further, adaptors for the user interface have to be developed to be able to interact with d3 visualizations.

  • Expected results

    • Every currently supported visualization metaphor can be generated in d3 using react components
    • The user interface can interact with d3

  • Involved Technologies
    Java, Xtend, Xtext, JavaScript, d3, react

  • Knowledge Prerequisite
    The challenge in this project is the diversity of technologies you will need. You will have to write Java and JavaScript code. You should already be familiar with Java or JavaScript, ideally with both. We don't expect you to know xtext or xtend. Experience with react and/or d3 is not necessary, but helpful. It is important that you are willing to learning and want to dive into new technologies.

  • Mentor
    David Baum [david.baum(at)uni-leipzig.de]

Visualization metaphors

  • Brief explanation
    Currently, ...

  • Expected results

    • ...

  • Involved Technologies
    Java, Xtend, Xtext, x3d, x3dom

  • Knowledge Prerequisite
    Experience with at least one high-level language, e.g. Java or C++. Experience with x3d/x3dom is not necessary.

  • Mentor
    David Baum [david.baum(at)uni-leipzig.de]

User Interface

Multiple Visualization at the same UI

  • Brief explanation
    So far, only a single view of one model is visualized at the same time. However, for many purposes it is necessary to simultaneously analyse more than one view of the model or to analyse multiple views of different models, e.g. comparing two versions of the same system.

  • Expected results
    The main result of this idea is, that the UI can handle multiple views of the same model or different models. As a secund result it should be possible to couple this views, so an user event in one view has also an effekt at the other view. For example the selection of an element in the first view selects also the element at the second view, if it exists and if it's displayed.

  • Involved Technologies
    JavaScript, x3dom

  • Knowledge Prerequisite
    Experience with JavaScript. Experience with x3d/x3dom is not necessary.

  • Mentor
    Pascal Kovacs [pkovacs(at)uni-leipzig.de]

Ruby Extractor

Dashboard

d3 software visualization components

  • Brief explanation
    The web-based software visualization dashboard supports software project managers in decision making. Its data source is an existing neo4j database with structural, behavioral, and evolutionary information of a software project. The dashboard consists of interactive react components where each supports a certain task, e.g. hotspot or test coverage analysis. Every component encapsulates a cypher query to fetch data from the existing neo4j database and d3 code for visualizing its results.

  • Expected results

    • The software visualization dashboard is extended by a new component that supports a software project manager in decision making

  • Involved Technologies
    JavaScript, react, d3, neo4j

  • Knowledge Prerequisite
    The challenge in this project is to find a suitable visualization that supports a software project manager and that can be build on the basis of the existing data in the neo4j database. You will have to write JavaScript and react code. You should already be familiar with JavaScript or react, ideally with both. Experience with d3 and/or neo4j cypher queries is not necessary, but helpful. You can either reuse existing d3 components or develop your own d3 visualization and you are supported with cypher queries by the mentor. It is important that you are willing to learning and want to dive into new technologies.

  • Mentor
    Richard Müller [rmueller(at)wifa.uni-leipzig.de]

Clone this wiki locally