Skip to content

Commit c57e568

Browse files
committed
Removed asciidoc support and rewrote vast2021 in markdown
1 parent d474d18 commit c57e568

File tree

4 files changed

+35
-45
lines changed

4 files changed

+35
-45
lines changed

Gemfile

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,3 @@ versions = JSON.parse(open('https://pages.github.com/versions.json').read)
77
gem 'github-pages', group: :jekyll_plugins
88
gem 'kramdown', ">= 2.3.1"
99
gem 'jekyll-seo-tag'
10-
11-
group :jekyll_plugins do
12-
gem 'jekyll-asciidoc'
13-
end

Gemfile.lock

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ GEM
99
zeitwerk (~> 2.2, >= 2.2.2)
1010
addressable (2.7.0)
1111
public_suffix (>= 2.0.2, < 5.0)
12-
asciidoctor (2.0.16)
1312
coffee-script (2.4.1)
1413
coffee-script-source
1514
execjs

_config.yml

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,11 @@ twitter_username: jandot
1010
permalink: /:year/:month/:title
1111
logo: /assets/vda-lab_logo.png
1212

13-
asciidoc: {}
14-
asciidoctor: {}
15-
1613
# Build settings
1714
markdown: kramdown
1815

1916
plugins:
2017
- jekyll-seo-tag
21-
- jekyll-asciidoc
2218

2319
exclude:
2420
- svelte-components
Lines changed: 35 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -1,68 +1,70 @@
1-
= VAST Challenge 2021 - Award for Strong Support for Visual Exploration
2-
:page-layout: page
3-
:page-permalink: /vast2021.html
1+
---
2+
layout: page
3+
title: VAST Challenge 2021 - Award for Strong Support for Visual Exploration
4+
permalink: vast2021.html
5+
---
46

5-
image:http://vda-lab.github.io/assets/vast2021_teaser.jpeg[rotate=25]
7+
<img src="{{site.baseurl}}/assets/vast2021_teaser.jpeg" />
68

7-
From the https://vast-challenge.github.io/2021/about.html[VAST challenge webpage]: "The goal of the annual IEEE Visual Analytics Science and Technology (VAST) Challenge is to advance the field of visual analytics through competition."
9+
From the [VAST challenge webpage](https://vast-challenge.github.io/2021/about.html): "The goal of the annual IEEE Visual Analytics Science and Technology (VAST) Challenge is to advance the field of visual analytics through competition."
810

911
The VAST challenge is a prime opportunity for teambuilding in a visual analytics lab, and our contribution won the **Award for Strong Support for Visual Exploration**. It's a good example of a problem that cannot be solved _without_ involving (interactive) data visualisations.
1012

1113
In this year's challenge, we try to find out why and how a group of employees disappear from a natural gas production site. All fictitious, of course.
1214

13-
Note: a more complete description of this work can be found in http://vda-lab.github.io/assets/vast2021_paper.pdf[our paper]. http://vda-lab.github.io/assets/vast2021_video.wmv[This video] also goes over the same material in more detail and shows the actual interactivity.
15+
Note: a more complete description of this work can be found in [our paper](http://vda-lab.github.io/assets/vast2021_paper.pdf). [This video](http://vda-lab.github.io/assets/vast2021_video.wmv) also goes over the same material in more detail and shows the actual interactivity.
1416

15-
== The question
16-
For the complete brief, see https://vast-challenge.github.io/2021/MC2.html[https://vast-challenge.github.io/2021/MC2.html]. All names, companies and locations (e.g. islands) are fictional.
17+
## The question
18+
For the complete brief, see [https://vast-challenge.github.io/2021/MC2.html](https://vast-challenge.github.io/2021/MC2.html). All names, companies and locations (e.g. islands) are fictional.
1719

1820
_In the roughly twenty years that the GAStech company has been operating a natural gas production site in the island country of Kronos, it has produced remarkable profits and developed strong relationships with the government of Kronos. However, GAStech has not been as successful in demonstrating environmental stewardship._
1921

2022
_In January, 2014, the leaders of GAStech are celebrating their new-found fortune as a result of the initial public offering of their very successful company. In the midst of this celebration, several employees of GAStech go missing. An organization known as the Protectors of Kronos (POK) is suspected in the disappearance, but things may not be what they seem._
2123

2224
_You are called in to help law enforcement from Kronos and Tethys. Was it a kidnapping? Was something else going on?_
2325

24-
== The data
26+
## The data
2527
The data available consisted of geospatial tracking data of company cars, car assignments (which employee uses which car), a touristic map of the island that the company is located on, as well as credit card and loyalty card transactions of the two weeks leading up to the employees’ disappearance. We wanted to identify suspicious behaviours or patterns.
2628

2729
What the data looks like:
2830

2931
* corporate car assignments (44 records)
30-
32+
<pre>
3133
lastname firstname car_id employment_type employment_title
3234
Calixto Nils 1 Information Technology IT Helpdesk
3335
Azada Lars 2 Engineering Engineer
3436
Balas Felix 3 Engineering Engineer
35-
37+
</pre>
3638
* car GPS tracking data (for the 2 weeks preceding the event; 685,169 records)
37-
39+
<pre>
3840
timestamp id lat long
3941
01/06/2014 06:28:01 35 36.0762253 24.87468932
4042
01/06/2014 06:28:01 35 36.07622006 24.87459598
4143
01/06/2014 06:28:03 35 36.07621062 24.87444293
42-
44+
</pre>
4345
* credit card transactions (for the 2 weeks preceding the event; 1,490 records)
44-
46+
<pre>
4547
timestamp location price last4ccnum
4648
01/06/2014 07:28 Brew've Been Served 11.34 4795
4749
01/06/2014 07:34 Hallowed Grounds 52.22 7108
4850
01/06/2014 07:35 Brew've Been Served 8.33 6816
49-
51+
</pre>
5052
* loyalty card data (for the 2 weeks preceding the event; 1,393 records)
51-
53+
<pre>
5254
timestamp location price loyaltynum
5355
01/06/2014 Brew've Been Served 4.17 L2247
5456
01/06/2014 Brew've Been Served 9.6 L9406
5557
01/06/2014 Hallowed Grounds 16.53 L8328
5658
...
57-
59+
</pre>
5860
* tourist map of the area
5961

60-
image:http://vda-lab.github.io/assets/vast2021_touristmap.jpg[width=75%]
62+
<img src="{{site.baseurl}}/assets/vast2021_touristmap.jpg" width="75%"/>
6163

6264
* shapefile of the island (3,290 records)
6365

64-
image:http://vda-lab.github.io/assets/vast2021_geojson.png[width=50%]
65-
66+
<img src="{{site.baseurl}}/assets/vast2021_geojson.png" width="50%"/>
67+
<pre>
6668
{ "type": "Feature",
6769
"properties": { "Name": "N Hallanol Dr"},
6870
"geometry": { "type": "LineString",
@@ -72,41 +74,38 @@ image:http://vda-lab.github.io/assets/vast2021_geojson.png[width=50%]
7274
"geometry": { "type": "LineString",
7375
"coordinates": [ [ 24.847478, 36.048091 ], [ 24.848369, 36.048074 ] ] } },
7476
...
75-
77+
</pre>
7678
Here's an overview of the data and how they are related:
7779

78-
image:http://vda-lab.github.io/assets/vast2021_data_overview.png[width=75%]
80+
<img src="{{site.baseurl}}/assets/vast2021_data_overview.png" width="75%"/>
7981

8082
Three of these data sources share time as a common attribute. However, their granularity differed: GPS traces were accurate to the second, credit card transactions to the minute, and loyalty card transactions to the day.
8183

82-
== Our approach
84+
## Our approach
8385
First, we matched the transactions of loyalty cards and credit cards, assuming each employee has one of each but allowing for more complex relations. Then, we simultaneously matched cars to loyalty-credit card matches and businesses to GPS positions where cars were stationary (i.e. points of interest; POIs). Finally, we analysed meetings of people, looking for suspicious patterns.
8486

85-
=== Matching credit cards with loyalty cards
86-
image:http://vda-lab.github.io/assets/vast2021_data_match1.png[width=50%]
87+
### Matching credit cards with loyalty cards
88+
<img src="{{site.baseurl}}/assets/vast2021_data_match1.png" width="50%"/>
8789

8890
We first matched credit cards with loyalty cards. We used two metrics: (1) the correlation between vectors indicating the total amount of money spent at each business on each day, and (2) the Jaccard index of card’s transaction sets, where transactions are equal when they occur at the same business on the same day for the same price.
8991

90-
We created two main visuals: a bipartite graph linking these two types of cards and a detailed view showing each selected credit
91-
card’s transactions on a time-axis coloured by the matching loyalty card in a small multiple for each day.
92-
image:http://vda-lab.github.io/assets/vast2021_matches.jpeg[]
93-
image:http://vda-lab.github.io/assets/vast2021_transactionmatches.png[width=75%]
92+
We created two main visuals: a bipartite graph linking these two types of cards and a detailed view showing each selected creditcard’s transactions on a time-axis coloured by the matching loyalty card in a small multiple for each day.
93+
<img src="{{site.baseurl}}/assets/vast2021_matches.jpeg" />
94+
<img src="{{site.baseurl}}/assets/vast2021_transactionmatches.png" width="75%"/>
9495

9596
Using these interfaces we were able to correctly match the cards and also discovered two data issues: transactions for one particular business always occurred one day earlier in the loyalty card data than in the credit card data, and some credit card transactions were precisely 20, 24, 60, or 80 units higher than their only potential matching loyalty card transaction.
9697

97-
=== Matching credit cards to cars, and finding businesses
98-
image:http://vda-lab.github.io/assets/vast2021_data_match2.png[width=50%]
98+
### Matching credit cards to cars, and finding businesses
99+
<img src="{{site.baseurl}}/assets/vast2021_data_match2.png" width="50%"/>
99100

100101
Here's an overview of the approach used:
101-
image:http://vda-lab.github.io/assets/vast2021_fig18.png[]
102+
<img src="{{site.baseurl}}/assets/vast2021_fig18.png" width="75%"/>
102103

103104
Transactions of high-rated matches were manually assigned to periods when cars were stationary, introducing POI-to-business constraints and removing the transaction and stationary period from consideration in other matches.
104105

105106
Using these interfaces we found several data issues, including a business whose credit card transaction times were always approximately 12 hours too late, and a car that had consistent GPS offset. We also used the interface to find out where everyone lived, based on where there cars were parked overnight.
106107

107-
=== Investigating interactions between employees
108+
### Investigating interactions between employees
108109
Now that all links are made (i.e. we know who was where at what time) we wanted to investigate any suspicious patterns. We found a surprise party for a particular employee one evening, a nightly guard duty at executives’ homes, two employees who meet for long lunches at the hotel, and executives who played golf together. Apart from identifying the businesses and employees' homes, we also found other locations of interest, that were later explained to be safe houses.
109110

110-
For a more complete description of the analyses and visuals, as well as more of the insights we obtained, see http://vda-lab.github.io/assets/vast2021_paper.pdf[our paper].
111-
112-
111+
For a more complete description of the analyses and visuals, as well as more of the insights we obtained, see [our paper](http://vda-lab.github.io/assets/vast2021_paper.pdf).

0 commit comments

Comments
 (0)