search

holoviz-topics / examples

Visualization-focused examples using HoloViz for specific topics
https://examples.holoviz.org
Creative Commons Attribution 4.0 International
84 stars 25 forks source link

World Cup 2018 example #402

Closed Azaya89 closed 3 months ago

Azaya89 commented 5 months ago

As part of the NumFocus SDG initiative, this example aims to enrich the HoloViz examples website by introducing a sports-related topic, specifically focusing on the 2018 FIFA World Cup. The motivation behind this addition is to diversify the range of topics covered by the examples, thereby making the website more comprehensive and appealing to a broader audience.

Motivation and Objectives

The primary motivation for this example is to demonstrate the capabilities of the HoloViz ecosystem in analyzing and visualizing sports data. By incorporating the relatively new pn.bind API from the Panel library, as well as various widgets, this example showcases how interactive and dynamic visualizations can be created to represent events on a football pitch during a typical competitive match. This serves to address the current gap in sports-related examples on the HoloViz website.

Investigation Questions

The notebook seeks to answer several key questions through data analysis and visualization:

Inspiration and Sources

The inspiration for this example comes from a deep interest in football and a desire to apply data visualization techniques to sports analytics. The data used in this notebook is sourced from Pappalardo, Luca; Massucco, Emanuele (2019). Soccer match event dataset. figshare. Collection.

This project also draws inspiration from existing sports analytics studies and visualizations, aiming to provide similar insights using the HoloViz tools.

Visual Highlights

https://github.com/user-attachments/assets/222314cf-7517-4767-a4c7-721a775f82a4

Contribution to the HoloViz Community

By adding this example, we hope to achieve several goals:

github-actions[bot] commented 5 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).

github-actions[bot] commented 4 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).

github-actions[bot] commented 4 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).

droumis commented 4 months ago

@Azaya89 , could you add a full description to the PR here including motivation, what you're hoping to achieve in terms of addressing any gaps in HoloViz examples API and topic-wise, what investigation questions you're hoping to answer, citing any sources or inspiration, maybe a pic or two, and that this is part of a numfocus-funded initiative?

Azaya89 commented 4 months ago

@Azaya89 , could you add a full description to the PR here including motivation, what you're hoping to achieve in terms of addressing any gaps in HoloViz examples API and topic-wise, what investigation questions you're hoping to answer, citing any sources or inspiration, maybe a pic or two, and that this is part of a numfocus-funded initiative?

Done!

droumis commented 4 months ago

Great! Could you add links to the data source and related paper (in both the PR description and overview within the example notebook)

Azaya89 commented 4 months ago

Great! Could you add links to the data source and related paper (in both the PR description and overview within the example notebook)

There is already a link to the data source in the notebook. I've added same to this PR description now...

github-actions[bot] commented 4 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).

droumis commented 4 months ago

Hi @Azaya89 , I went ahead and committed all the suggestions I made above in my review, except I did not change the thumbnail. I'll leave that for you to decide.

github-actions[bot] commented 4 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).

github-actions[bot] commented 4 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).

github-actions[bot] commented 4 months ago

Your changes were successfully integrated in the dev site, make sure to review the pages of the projects you touched before merging this PR: https://holoviz-dev.github.io/examples/. You can also download an archive of the site from the workflow summary page which comes in handy when your dev site built was overriden by another PR (we have a single dev site!).