Final - Reno, Wasserman, and Yoder #12

New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
JuniorJedi490 wants to merge 148 commits into cs480x-22c:main from JuniorJedi490:main
CS 480x final project Process Book.pdf
Binary file not shown.
README.md
            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -1,123 +1,16 @@
  
    Final Project - Interactive Data Visualization  

    ===

    The key learning experience of this course is the final project. 

    You will design a web site and interactive visualizations that answer questions you have, provide an exploratory interface to some topic of your own choosing, or take on a more ambitious experiment than A3. 

    You will acquire the data, design your visualizations, implement them, and critically evaluate the results. 

    The following is the link to our visualization which is hosted using git gh-pages: https://juniorjedi490.github.io/final/. 

    The path to a good visualization is going to involve mistakes and wrong turns. 

    It is therefore important to recognize that mistakes are valuable in finding the path to a solution, to broadly explore the design space, and to iterate designs to improve possible solutions. 

    To help you explore the design space, we will hold events such as feedback sessions in which you propose your idea and initial designs and receive feedback from the class and staff.

    The video for our presentation is in our Git repository in the videos folder (csfinal-Large 540p.mov). It is also available on YouTube at this link: https://youtu.be/RBVVKYBsrto. 

    Proposals / Idea Generation

    ---

    Our data is available in our Git repository. ssv_data.csv is the original data we collected, and data.json is this data in json format. 

    Submit project ideas using [this Google Form](https://docs.google.com/forms/d/e/1FAIpQLSepaCzjEq9AXwmJ8mJ-06ytkQUuLI1Z2QF5KGyhVnKaxBI-mA/viewform?usp=sf_link).

    Our code is index.html, script.js, style.js, and tojson.R. csv_data.csv, data.json, and data2.json are our data. We use data.json in script.js to create the visualization which appears in/on index.html via the link at the top of the readme. 

    You're encouraged to submit many ideas-- staff will help you identify the most promising ones and possible roadblocks.

    In script.js we create arrays using data from data.json that are similar to the json format that the example (https://observablehq.com/@mbostock/hello-cola) that we based on visualization off of uses. A nodes and a links array. We than use d3 to create our visualization.

    Please stick to 1-4 folks per team.

    Our visualization features a node/link graph where each node is a species of generation 1 Pokemon. Each node is colored based on the species’ type, and if the Pokémon has two types, the second type informs the color of the node’s outline stroke color. The size of each node’s radius is scaled based on the sum of the following statistics: base HP, base Attack, base Defense, base Speed, and base Special. Each node has a link to any other node that shares one (or both) of its type(s). This leads to the nodes clustering based on shared types in the visual, making it clear how the original game’s Pokémon selection spreads across the different types.

    Final Project Materials

    ---

    For your final project you must hand in the following items.

    ### Process Book

    An important part of your project is your process book. Your process book details your steps in developing your solution, including the alternative designs you tried, and the insights you got. Develop your process book out of the project proposal. Equally important to your final results is how you got there! Your process book is the place you describe and document the space of possibilities you explored at each step of your project. It is not, however, a journal or lab notebook that describes every detail - you should think carefully about the important decisions you made and insights you gained and present your reasoning in a concise way.

    We strongly advise you to include many figures in your process book, including photos of your sketches of potential designs, screen shots from different visualization tools you explored, inspirations of visualizations you found online, etc. Several images illustrating changes in your design or focus over time will be far more informative than text describing those changes. Instead, use text to describe the rationale behind the evolution of your project.

    Your process book should include the following topics. Depending on your project type the amount of discussion you devote to each of them will vary:

    - Overview and Motivation: Provide an overview of the project goals and the motivation for it. Consider that this will be read by people who did not see your project proposal.

    - Related Work: Anything that inspired you, such as a paper, a web site, visualizations we discussed in class, etc.

    - Questions: What questions are you trying to answer? How did these questions evolve over the course of the project? What new questions did you consider in the course of your analysis?

    - Data: Source, scraping method, cleanup, etc.

    - Exploratory Data Analysis: What visualizations did you use to initially look at your data? What insights did you gain? How did these insights inform your design?

    - Design Evolution: What are the different visualizations you considered? Justify the design decisions you made using the perceptual and design principles you learned in the course. Did you deviate from your proposal?

    - Implementation: Describe the intent and functionality of the interactive visualizations you implemented. Provide clear and well-referenced images showing the key design and interaction elements.

    - Evaluation: What did you learn about the data by using your visualizations? How did you answer your questions? How well does your visualization work, and how could you further improve it?

    As this will be your only chance to describe your project in detail make sure that your process book is a standalone document that fully describes your results and the final design. 

    [Here](http://dataviscourse.net/2015/assets/process_books/bansal_cao_hou.pdf) are a [few examples](http://dataviscourse.net/2015/assets/process_books/walsh_trevino_bett.pdf) of process books from a similar course final.

    Tip: Start your process book on Day 1. Make entries after each meeting, and trim / edit as needed towards the end of the project. Many folks use either slides software (like PowerPoint) or Google Docs to make this book, as both allow for flexible layouts and export to PDF.

    ### Project Website

    Create a public website for your project using GitHub pages or another web hosting service of your choice. 

    The web site should contain your interactive visualization, summarize the main results of the project, and tell a story. 

    Consider your audience (the site should be public if possible, unless you're running an experiment, etc.) and keep the level of discussion at the appropriate level. 

    Your process book and data should be linked from the web site as well. 

    Also embed your interactive visualization and your screen-cast in your website. 

    If you are not able to publish your work (e.g., due to confidential data) please let us know in your project proposal.

    ### Project Screen-Cast

    Each team will create a two minute screen-cast with narration showing a demo of your visualization and/or some slides. 

    You can use any screencast tool of your choice, such as Camtasia or Loom (new and recommended). 

    Please make sure that the sound quality of your video is good -- it may be worthwhile to invest in an external USB microphone-- campus IT should have some you can borrow. 

    Upload the video to an online video-platform such as YouTube or Vimeo and embed it into your project web page. 

    For our final project presentation day, we will show as many videos in class as possible, and ask teams to field questions.

    We will strictly enforce the two minute time limit for the video, so please make sure you are not running longer. 

    Use principles of good storytelling and presentations to get your key points across. Focus the majority of your screencast on your main contributions rather than on technical details. 

    What do you feel is the best part of your project? 

    What insights did you gain? 

    What is the single most important thing you would like your audience to take away? Make sure it is front and center rather than at the end.

    Outside Libraries/References

    ---

    For this project you *do not* have to write everything from scratch.

    You may *reference* demo programs from books or the web, and *include* popular web libraries like Material UI, React, Svelte, etcetera. 

    Please *do not* use libraries on top of d3 without consulting staff, however. 

    Libraries like nvd3.js look tempting, but such libraries often have poor defaults and result in poor visualizations.

    There may be exceptions.

    Instead, draw from the numerous existing d3 examples on the web.

    If you use outside sources please provide a References section with links at the end of your Readme.

    Resources

    ---

    The "[Data is Plural](https://tinyletter.com/data-is-plural/archive)" weekly letter often contains interesting datasets.

    Think of something you're interested in, go find data on it! Include data collection and processing as part of your work on this project.

    Requirements

    ---

    Store the following in your GitHub repository:

    - Code - All web site files and libraries assuming they are not too big to include

    - Data - Include all the data that you used in your project. If the data is too large for github store it on a cloud storage provider, such as Dropbox or Yousendit.

    - Process Book- Your Process Book in PDF format.

    - README - The README file must give an overview of what you are handing in: which parts are your code, which parts are libraries, and so on. The README must contain URLs to your project websites and screencast videos. The README must also explain any non-obvious features of your interface.

    GitHub Details

    ---

    - Fork the repo. You now have a copy associated with your username.

    - Make changes to index.html to fulfill the project requirements. 

    - Make sure your "main" branch matches your "gh-pages" branch. See the GitHub Guides referenced above if you need help.

    - Edit the README.md with a link to your gh-pages or other external site: for example http://YourUsernameGoesHere.github.io/DataVisFinal/index.html

    - To submit, make a [Pull Request](https://help.github.com/articles/using-pull-requests/) on the original repository.

    Grading

    ---

    - Process Book - Are you following a design process that is well documented in your process book?

    - Solution - Is your visualization effective in answering your intended questions? Was it designed following visualization principles?

    - Implementation - What is the quality of your implementation? Is it appropriately polished, robust, and reliable?

    - Presentation - Are your web site and screencast clear, engaging, and effective?

    Your individual project score will also be influenced by your peer evaluations.

    References

    ---

    - This final project is adapted from https://www.dataviscourse.net/2020/project/

    We have a legend on the right of the visualization which shows what color is associated with each type of Pokemon.
_config.yml
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		theme: jekyll-theme-minimal
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Final - Reno, Wasserman, and Yoder #12

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Final - Reno, Wasserman, and Yoder #12

Are you sure you want to change the base?

Uh oh!

Final - Reno, Wasserman, and Yoder #12

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!
