Skip to content
This repository was archived by the owner on May 17, 2025. It is now read-only.

siddydutta/Multiview-Visualisation-Systems

Repository files navigation

Multiview Visualisation Systems

COMPSCI5099 Information Visualisation M - 2024-25

This repository contains the coursework submission for the Information Visualisation course. It involves using a publicly available dataset to build three different multi-view visualisation systems that can perform the same four tasks, and a user evaluation based on the same.

Dataset used from World Weather Repository (Daily Updated) on Kaggle. (extracted on 2024-02-22)

Artefacts

Demo Video | YouTube

Development

Conda Environment

conda env create -f environment.yml
conda activate infoviz
jupyter notebook

Data Processing

The Data Processing.ipynb notebook involves all the pre processing of the raw data including extracting the file, dropping miscellaneous columns, extrapolating columns and saving the cleaned data as EU-UK-Weather-Data.csv.

Use Data Directly

wget https://raw.githubusercontent.com/siddydutta/Multiview-Visualisation-Systems/refs/heads/main/EU-UK-Weather-Data.csv

Team Members

  1. Ankit Das - 📧 2980596D
  2. Bhavisha Jatin Dholakia - 📧 3050100D
  3. Dishani Sarkar - 📧 2979085S
  4. Rithik Sah - 📧 2980356S
  5. Siddhartha Pratim Dutta - 📧 2897074D

Assessment Feedback (27/30)

A. Design and implementation (20 marks overall)

  • Data (2/2). Good clear description of the original and derived data, using Munzner's taxonomy.
  • Tasks (2/2). The tasks chosen here show a good variety across Munzner's task taxonomy, and make sense given the context. Core systems (4/4). System A, initially at least, has too many colours mapped to cities. Location might distinguish them on the map, but not on the line charts. I suppose you have to just filter quickly. The demo didn't show it, but it seems that it has brushing on the map linked to the two line charts. I'm not sure that selection on the legend counts as brushing, and it doesn't seem like bidirectional (as other controls don't change the legend, I think, e.g. I don't think Valletta ever gets snow). B has brushing on the timeline, linked to the other lat/lon chart. Interesting setup, with a small region around a city's location having the data for that city laid out in a rectangular area. And -- hooray! -- B shows generalised selection, moving up a time hierarchy from a selected city. It seems to have bidirectional linking. Also good to see that C has multi-way linkage between its three charts. Good work here -- very few groups did more than one-way linking, and fewer did GS.
  • Generalised selection (4/4). See above. I saw in labs that the most feasible way to do this was via external buttons or toggles, rather than some interaction in the middle of a chart (e.g. shift-click to go up)... but that's fine. The time hierarchy makes sense as a semantic structure, and the traversal policy follows from the semantics (as it should).
  • Demo (yes)
  • Design comparison (7/8). Good discussion here, although it would have been good to consistently see the best choice argued for, as per the spec. Sometimes the text here just said what each choice was like, but didn't make such a case.

B. Evaluation (10 marks overall)

  • user evaluation comparison (6/8). Good data collection here, with a useful range of data collected. Well done for randomising the order of tasks. Apparently a good amount of qualitative data was collected, but there is almost nothing about the analysis/findings from it in this section. This seems like a gap or loss, although some of this appears in the future work section.
  • future work (2/2). All pretty sensible recommendations, well grounded in the evaluation data.

2+2+4+4+7+6+2 = 27/30