Difference between revisions of "VAProject"

From Visual Analytics and Applications
Jump to navigation Jump to search
 
(14 intermediate revisions by the same user not shown)
Line 41: Line 41:
 
The project proposal should describe the motivation of the project, problems or issues that the project will address, the relevant related work, the approach the team plans to take to solve the problem, and early prototypes or storyboards.  The project teams should take advantage of this proposal as a chance to get feedback on the direction of the project from their peers.
 
The project proposal should describe the motivation of the project, problems or issues that the project will address, the relevant related work, the approach the team plans to take to solve the problem, and early prototypes or storyboards.  The project teams should take advantage of this proposal as a chance to get feedback on the direction of the project from their peers.
  
In '''week 14''', all project teams will give a 30-minutes presentation at the Visual Analytics workshop outlining the motivation of the project, design principles, implementation process, analytical methods used and findings of their project.  <del>This will follow by an evening poster presentation session.</del>   
+
<del>In '''week 14''', all project teams will give a 30-minutes presentation at the Visual Analytics workshop outlining the motivation of the project, design principles, implementation process, analytical methods used and findings of their project.  This will follow by an evening poster presentation session.</del>.  The workshop and poster sessions have been cancelled due to COVID19.  
  
Students are required to update their project wiki with all the details including the final implementation, user guide and lesson learned by '''the end of week 14'''.  They are also required to upload the artifact including the application onto e-Learn.   
+
Students are required to update their project blog with all the details including the final implementation, user guide and lesson learned by '''the end of week 14'''.  They are also required to upload the artifact including the application onto e-Learn.   
  
 
Additional materials will be uploaded into course wiki and explain in class to assist students with topics selection, project design, postal presentation, and research paper writing.
 
Additional materials will be uploaded into course wiki and explain in class to assist students with topics selection, project design, postal presentation, and research paper writing.
Line 51: Line 51:
 
   
 
   
 
*  Formulation of project ideas and create project page on course wiki: by the end of '''Week 7'''.
 
*  Formulation of project ideas and create project page on course wiki: by the end of '''Week 7'''.
*  <del>Submission of project poster: by 9.00am 22nd April 2020.</del>
+
*  <del>Submission of project poster: by 9.00am 21st April 2021.</del>
*  <del>Visual Analytics Workshop and Poster: 25th April 2020, 9:00am-5:30pm</del>
+
*  <del>Visual Analytics Workshop and Poster: 24th April 2021, 9:00am-5:30pm </del>
*  Submission of final project paper and artifacts: 26th April 2020 by 11:59pm (mid-night)
+
*  Submission of final project poster, practice research paper and artifacts: 25th April 2021 by 11:59pm (mid-night)
  
  
 
== Project Deliverables ==
 
== Project Deliverables ==
 +
===Project Blog Page===
  
===Project Wiki===
+
====Project Github====
  
As a first step, you should create a project wiki (in the form of a wiki page) that includes:
+
At the beginning of the project, project teams are required to create a project Github.  The project Github should include all the materials used to develop the project and the written materials such as proposal, poster and practice research paper.  It must be used to maintain a complete project versioning including the application and project documents.  The Github link must be included in the project proposal.  By the end of the project, the project team must pack the final version of the Github repository and upload onto eLearn for final submission.  The Github link also must be provided on eLearn. 
 +
 
 +
====Project Blog Webpage====
 +
In previous terms, SMU wiki are used to disseminate Visual Analytics Project.  For this term, blogdown from RStudio will be used to create the project website and will be disseminated by using webserver such as Netfity.
 +
 
 +
As a first step, you should create a project summary at the course wiki that includes:
  
 
* The title of your project,
 
* The title of your project,
 
* A short description of not more than 350 word summarising the motivation, objectives, main features of the application your team are going to build, and
 
* A short description of not more than 350 word summarising the motivation, objectives, main features of the application your team are going to build, and
* The project proposal.  This should in a separate wiki page.
+
* The project proposal.  This should in a webblog page (remember to provide a link at the wiki).
* Link to project poster
 
* Link to the final ShinyApp
 
* Link to user guide
 
* Link to practice research paper
 
 
 
Please refer to the last section of this page for instructions on making the wiki page for the visual analytics project.  This sample assignment page gives an example of the kind of the page format you might wish to use for the project.
 
  
  
Line 94: Line 94:
 
Please ensure that the poster is in high resolution.  
 
Please ensure that the poster is in high resolution.  
  
The course instructor will be responsible for printing your poster. You are required to upload your posters to the '''wiki''' page of your project one week and your project '''Dropbox''' before the poster presentation.
+
Project teams are encouraged to use [https://github.com/brentthorne/posterdown/wiki posterdown] to design your poster.
 +
 
 +
The course instructor will be responsible for printing your poster. You are required to upload your posters to the '''blog''' page of your project one week and your project '''Dropbox''' before the poster presentation.
  
 
'''Note: The poster will be considered a final deliverable, so don't forget to apply good visual design and data visualisation principles and best practice to your poster.'''
 
'''Note: The poster will be considered a final deliverable, so don't forget to apply good visual design and data visualisation principles and best practice to your poster.'''
Line 100: Line 102:
  
 
===Visual Analytics Practice Research Paper===
 
===Visual Analytics Practice Research Paper===
 
*  a practice research paper ('''not more than 6 pages''' excluding figures, tables, formula and references) 
 
** [[File:Research_Paper_Template.doc|Research Paper Template]]
 
  
 
The research paper should be in the form of Visual Analytics Application practice and research.  In particular it should contain the followings:  
 
The research paper should be in the form of Visual Analytics Application practice and research.  In particular it should contain the followings:  
Line 117: Line 116:
  
 
*  Future Work - A description of how your system could be extended or refined.
 
*  Future Work - A description of how your system could be extended or refined.
 +
 +
The research paper should include an abstract of not more than 300 words.  The actual research paper itself should '''not more than 6 pages''' excluding figures, tables, formula and references.  The practice research paper must be edited by using '''R Markdown''' and the '''ACM: Association for Computing Machinery''' template of [https://github.com/rstudio/rticles '''rticle'''] should be used.
 +
  
 
==== Sample practice research papers ====
 
==== Sample practice research papers ====
  
* [https://ink.library.smu.edu.sg/sis_research/1761/ DIVAD: A Dynamic and Interactive Visual Analytical Dashboard for Exploring and Analyzing Transport Data]  
+
* [https://ink.library.smu.edu.sg/sis_research/1761/ DIVAD: A Dynamic and Interactive Visual Analytical Dashboard for Exploring and Analyzing Transport Data]
 +
* [https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-020-3494-x MEPHAS: an interactive graphical user interface for medical and pharmaceutical statistical analysis with R and Shiny]  
 
* [https://cran.r-project.org/web/packages/SpatialEpiApp/vignettes/manual.pdf SpatialEpiApp: A Shiny Web Application for the Analysis of Spatial and Spatio-Temporal Disease Data]
 
* [https://cran.r-project.org/web/packages/SpatialEpiApp/vignettes/manual.pdf SpatialEpiApp: A Shiny Web Application for the Analysis of Spatial and Spatio-Temporal Disease Data]
 
* [https://iopscience.iop.org/article/10.1088/1755-1315/20/1/012014 Developing web-based data analysis tools for precision farming using R and Shiny]
 
* [https://iopscience.iop.org/article/10.1088/1755-1315/20/1/012014 Developing web-based data analysis tools for precision farming using R and Shiny]
Line 133: Line 136:
 
*  artifact, an implementation of your system (source code and executable)
 
*  artifact, an implementation of your system (source code and executable)
 
*  User Guide - Step-by-step guide on how to use the data visualisation functions designed.  
 
*  User Guide - Step-by-step guide on how to use the data visualisation functions designed.  
** [[File:UG1.pdf|Sample UserGuide 1]]
+
** [https://wiki.smu.edu.sg/1920t2isss608/Group11_user_guide Sample UserGuide 1]
** [[File:UG2.pdf|Sample UserGuide 2]]
+
** [https://wiki.smu.edu.sg/1920t2isss608/img_auth.php/0/02/ISSS608_Group02_UserGuide.pdf Sample UserGuide 2]
 
*  project poster
 
*  project poster
 
*  a practice research paper
 
*  a practice research paper
Line 145: Line 148:
 
The visual analytics project will account for 30% of your final grade in the course.  The distribution of marks for each stage of the project are as follows:
 
The visual analytics project will account for 30% of your final grade in the course.  The distribution of marks for each stage of the project are as follows:
  
* Wiki 20%
+
* Project blog 20%
 
* Poster 10%
 
* Poster 10%
 
* <del>Workshop presentation 20%</del>
 
* <del>Workshop presentation 20%</del>
* Practice Research Paper 30%  
+
* Practice Research Paper 35%  
* Artifact 30%
+
* Artifact 35%
* User Guide 10%
 
 
   
 
   
 
The course instructor will consider strongly the novelty of the idea (If it has never been done before, you will get lots of credit!), how it addresses the problem at hand, the methodology you employ in doing the research, and your technical skill in implementing the idea.  
 
The course instructor will consider strongly the novelty of the idea (If it has never been done before, you will get lots of credit!), how it addresses the problem at hand, the methodology you employ in doing the research, and your technical skill in implementing the idea.  
Line 176: Line 178:
 
== Sample Projects ==
 
== Sample Projects ==
 
Note that the following examples are for references purposes.  You are urge to use your own creativity and innovation to design the application
 
Note that the following examples are for references purposes.  You are urge to use your own creativity and innovation to design the application
 
  
 
===MITB (Analytics)===  
 
===MITB (Analytics)===  

Latest revision as of 18:52, 12 April 2021

Vaa logo.jpg ISSS608 Visual Analytics and Applications

About

Weekly Session

DataViz Makeover

Assignment

Visual Analytics Project

Resources

 


Overview

The purpose of the project is to provide students first hand experience on collecting, processing and analysing large business data using real world data. A project may involve developing new methods or implementing visual analytics system to support analytic tasks in specific domains. Alternatively, a project may be in the form of application development by integrating analytical tools within a visual analytics environment. Students are encouraged to focus on research topics that are relevant to their field of study. It should address a concrete visual analytics problem and should propose a novel and creative solution.

The project is team work. Students are required to form a project team of 2-3 members by the first week of the academic term. Each project teams must start thinking about their project ideas after the first lesson. They are expected to discuss their project topic and scope of works with the instructor before the end of week 5. A project proposal in the form of blogdown on netfily will be prepared and the link must be provided on the course wiki by the end of week 7.

The project proposal should describe the motivation of the project, problems or issues that the project will address, the relevant related work, the approach the team plans to take to solve the problem, and early prototypes or storyboards. The project teams should take advantage of this proposal as a chance to get feedback on the direction of the project from their peers.

In week 14, all project teams will give a 30-minutes presentation at the Visual Analytics workshop outlining the motivation of the project, design principles, implementation process, analytical methods used and findings of their project. This will follow by an evening poster presentation session.. The workshop and poster sessions have been cancelled due to COVID19.

Students are required to update their project blog with all the details including the final implementation, user guide and lesson learned by the end of week 14. They are also required to upload the artifact including the application onto e-Learn.

Additional materials will be uploaded into course wiki and explain in class to assist students with topics selection, project design, postal presentation, and research paper writing.


Project Milestone

  • Formulation of project ideas and create project page on course wiki: by the end of Week 7.
  • Submission of project poster: by 9.00am 21st April 2021.
  • Visual Analytics Workshop and Poster: 24th April 2021, 9:00am-5:30pm
  • Submission of final project poster, practice research paper and artifacts: 25th April 2021 by 11:59pm (mid-night)


Project Deliverables

Project Blog Page

Project Github

At the beginning of the project, project teams are required to create a project Github. The project Github should include all the materials used to develop the project and the written materials such as proposal, poster and practice research paper. It must be used to maintain a complete project versioning including the application and project documents. The Github link must be included in the project proposal. By the end of the project, the project team must pack the final version of the Github repository and upload onto eLearn for final submission. The Github link also must be provided on eLearn.

Project Blog Webpage

In previous terms, SMU wiki are used to disseminate Visual Analytics Project. For this term, blogdown from RStudio will be used to create the project website and will be disseminated by using webserver such as Netfity.

As a first step, you should create a project summary at the course wiki that includes:

  • The title of your project,
  • A short description of not more than 350 word summarising the motivation, objectives, main features of the application your team are going to build, and
  • The project proposal. This should in a webblog page (remember to provide a link at the wiki).


Poster

The project poster should provide an overview of your project. It should include, but not limited to the following information:

  • Issues and problems - A clear statement of the issues or/and problems your project addresses.
  • Motivation - An explanation of why the issues and/or problems are interesting and what make them difficult to solve.
  • Approach - A description of the techniques or algorithms you used to solve the problem.
  • Results - Screenshots and a working demo of the system you built.
  • Future Work - An explanation of how the work could be extended.

The dimensions for the poster must conform to the International Standards Organization (ISO) poster size format (A1).

  • Size = ISO A1 (594 × 841mm or 23.39 × 33.11inci)
  • Resolution = 300dpi or above
  • File format = jpeg

Please ensure that the poster is in high resolution.

Project teams are encouraged to use posterdown to design your poster.

The course instructor will be responsible for printing your poster. You are required to upload your posters to the blog page of your project one week and your project Dropbox before the poster presentation.

Note: The poster will be considered a final deliverable, so don't forget to apply good visual design and data visualisation principles and best practice to your poster.


Visual Analytics Practice Research Paper

The research paper should be in the form of Visual Analytics Application practice and research. In particular it should contain the followings:

  • Motivation of the application
  • Review and critic on past works
  • Design framework - A detail description of the design principles used and data visualisation elements built (Refer to Section IV: Interface of this paper [1].
  • Demonstration - Use case
  • Discussion - What has the audience learned from your work? What new insights or practices has your system enabled? A full blown user study is not expected, but informal observations of use that help evaluate your system are encouraged.
  • Future Work - A description of how your system could be extended or refined.

The research paper should include an abstract of not more than 300 words. The actual research paper itself should not more than 6 pages excluding figures, tables, formula and references. The practice research paper must be edited by using R Markdown and the ACM: Association for Computing Machinery template of rticle should be used.


Sample practice research papers

Final Deliverables

The final deliverables will include:

  • artifact, an implementation of your system (source code and executable)
  • User Guide - Step-by-step guide on how to use the data visualisation functions designed.
  • project poster
  • a practice research paper

The final deliverables must be uploaded into the Dropbox of e-Learn (e.g. LMS). It must in a single zip file format.


Grading

The visual analytics project will account for 30% of your final grade in the course. The distribution of marks for each stage of the project are as follows:

  • Project blog 20%
  • Poster 10%
  • Workshop presentation 20%
  • Practice Research Paper 35%
  • Artifact 35%

The course instructor will consider strongly the novelty of the idea (If it has never been done before, you will get lots of credit!), how it addresses the problem at hand, the methodology you employ in doing the research, and your technical skill in implementing the idea.

In small group projects, each person will be graded individually. A good group project is a system consisting of a collection of well defined subsystems. Each subsystem should be the responsibility of one person and be clearly identified as their project. A good criteria for whether you should work in a group is whether the system as a whole is greater than the sum of its parts!

Grading criteria for poster

The poster will be graded based on the following criteria:

  • Clear communication of key aspects of solution
  • Clear communication of design approaches
  • Clear communication of arguments for proposed solution
  • Craft quality of the solution

Grading criteria for poster presentation

The poster presentation will be judged based on:

  • Clarity and organization of the oral presentation
  • Relevance and clarity of presentation material (poster and live demo,etc)
  • Quality of argument used to justify why the solution is worthy of consideration
  • Quality, originality and relevance of design solution


Sample Projects

Note that the following examples are for references purposes. You are urge to use your own creativity and innovation to design the application

MITB (Analytics)


Looking for Project?

VAST Challenge

  • VAST Challenge 2017 [15]
  • VAST Challenge 2016 [16]
  • VAST Challenge 2015 [17]
  • VAST Challenge 2014 [18]
  • VAST Challenge 2013 [19]
  • VAST Challenge 2012 [20]
  • VAST Challenge 2011 [21]

Other Source

  • Open Challenges at Visualizing Data [22]
  • Human Development Data Visualization Competition [23]
  • Bank of England: Data Visualisation Competition [24]