Grading

by Mike Gleicher on December 22, 2017

In case you’re wondering where grades came from…

Grading worked exactly as I said it would on the Course Policies.

For reading/discussion and seek and find, we used the scores. If you got nearly everything (missed a few, most of them complete) you got “full score” – which is the A/AB border. Each one counted for 1/3 of your grade.

The design challenges counted for the other 1/3. I computed things both weighting them evenly, and weighting them according to the number of weeks – and gave each person the one that was higher.

I then penalized people who missed a lot of the in-class assignments. (up to 1/2 grade)

I then penalized people who were chronically late. I considered anything with a day of a deadline ontime. I looked at the median lateness – if you were late more than you weren’t, there was a problem.

For people who were just below a grade boundary, I looked at the contents of your discussions and seek and finds. For a few people, I used this to give you an extra little bit if it made a difference. (it only could help)

No office hours on Wednesday, Dec 13

by Mike Gleicher on December 10, 2017

I need to cancel office hours on Wednesday, December 13th due to travel.

If you want to schedule something earlier in the day (or week) send me email.

The Week in Vis: Week 15 (Dec 11-Dec 15)

by gleicherapi on December 10, 2017

Week 15 (Mon, Dec 11-Fri, Dec 15) – The Finale!

We’ve gotten to the end of the semester.

Last week, we spoke about 3D and scientific visualization – although the two are really separate. Sadly we didn’t get to cover either in depth. Also, you (hopefully) are making good progress on design challenge 3.

This week, the topics are a little less focused. The “readings” cover two things that I wanted to get to in class, but may not get to discuss in lectures: animation and presentations. These are useful topics.

In class on Monday, we’ll talk about topic model visualization, in honor of a visitor (Prof. Eric Alexander, who got his start in visualization in the 2012 edition of this class). On Wednesday, we’ll have a “summary” lecture and I’ll talk about one of the last topics (presentations).

Remember that DC3 assignments are due on Sunday, December 17th. This is a pretty tight deadline – since I need to get grading done. (I am aware that I am behind on grading – in particular, I had hoped to get DC2 back to you).

If you haven’t already done so, please do the course evaluation aefis.wisc.edu.

Learning Goals (for this week)

This week is really “leftovers” – but these are two topics that I really want to be able to get to.

  1. Appreciate the “art” of presentations, and have some ways to think about it effectively to improve your own practice.
  2. Understand how animation can be used in visualization (and vice versa)

Office Hours (especially for DC3 Help)

by Mike Gleicher on December 6, 2017

I will hold extra office hours on Friday, 11-noon (basically the class time slot). This is a chance to come and ask DC3 questions (or any other questions you might have).

I may need to cancel office hours next week – so this might be your last chance to ask questions in person.

DC3 Examples

by Mike Gleicher on December 6, 2017

I have added more example networks to compare for DC3.

 

The Week in Vis: Week 14 (Dec 4-Dec 8)

by gleicherapi on December 3, 2017

Week 14 (Mon, Dec 4-Fri, Dec 8) – 3D and SciVis

Last week we talked about dimensionality reduction and graphs. We did demos for DC2 assignments (thanks again to all who participated!) And you (hopefully) all started DC3.

This week, we’ll have a completely different topic: traditional scientific visualization. However, before we get to that we need to talk about 3D. Both are topics that should be courses unto themselves. But hopefully, we can get some basics in place over the two days.

Learning Goals (for this week)

These are really two separate topics (although people often think of them together). And sadly in class, we barely get to scratch the surface of either.

  1. Understand how the basics of how the human visual system “sees” 3D, and the ramifications of this for visual design.
  2. Understand how different perceptual cues can be used to convey depth, and how they can be used in visual displays.
  3. Appreciate when 3D should and shouldn’t be used in visualization

And for SciVis…

  1. Understand the challenges of working with “traditional scientific” data sets and data types.
  2. Have a basic sense of the problems of field visualization (scalar fields, vector fields, …) and the basic approaches to these problems.
  3. Have an awareness of the basic approaches to the most common problems (2D scalar fields, 3D scalar fields (volume visualization), …)

DC3 has been posted!

by Mike Gleicher on November 25, 2017

Design Challenge 3 has been posted!

The sample data and code will be coming soon.

 

The Week in Vis: Week 13 (Nov 27-Dec 1)

by gleicherapi on November 25, 2017

Week 13 (Mon, Nov 27-Fri, Dec 1) – Graphs

Last week in class started to talk about scalability concerns, but took a pre-Thanksgiving detour to talk about DC3. We’ll discuss dimensionality reduction this coming week. And DC3 is posted (at least in draft form).

This week’s topic is graphs. Which will be useful for DC3. We’ll back up and talk about Dimensionality Reduction (because it’s an important topic, and a favorite of mine).

On Friday, December 1, there will be an optional class where you can give a demo of your DC2. This is your chance to show off what you’ve done – and see what others have done. You need to have handed in DC2 before this. (it is due on Sunday, 11/26 – and we’d prefer you turn it in and move on to DC3).

Learning Goals (for this week)

  1. Understand what graph and network data is and the specific challenges of it
  2. Be aware of a range of standard designs for graph data, beyond node-link diagrams
  3. Appreciate the challenges of node-link layout, and have a sense of the methods available

DC2 Demos

by Mike Gleicher on November 24, 2017

In class Wednesday, many people were interested in seeing what others have done for DC2. So, we’ll have a demo session in the class time slot on Friday, December 1st.

Showing off your DC2 is optional: we will grade them whether you give a demo or not. However, we will take the demo into account if you do one. It can only help you. If your assignment is better “on paper” than when you show it off, we’ll ignore the demo. If your demo is great, that can make up for other deficiencies.

Technically, we will accept late assignments on Friday – however, we will only let you do a demo if you have already turned in your assignment. We really want people moving onto DC3 (coming soon, as we discussed in class).

Some Notes:

  1. If you want us to see your program running, the demos are the only way to insure we see it live. We will try to run people’s programs (especially if it’s easy to just open a web page or something). But we cannot spend too much time during grading to try to make everything go.
  2. Demos aren’t limited to implementation assignments: you can show off your sketched design as well. That way you can describe the interactions you envisioned, or anything that was hard to draw.
  3. In theory, I would like to be “strict” on the 5 minutes per project. 1 minute to set up, 3 minutes to show off, 1 minute for questions. In practice, it’s hard to cut off interesting questions
  4. The room has a VGA connector – if you want to plug in your laptop, make sure to have an appropriate adapter (I will have a mini-DisplayPort -> VGA one). It’s probably best if you use your own laptop rather than relying on mine.
  5. You can use the document camera to show off things on paper as well.

DC2 Grading and Rubric

by Mike Gleicher on November 22, 2017

Everyone who turned in a draft should have gotten some (limited) feedback as a comment on Canvas. (note: I may not see any replies you make to those).

There is a link to a long list of common comments I made on assignments, so you can see the kinds of things I noticed on some assignments. (the list is here).

I also just posted a draft “rubric” that will give you a sense of the kinds of things we will be looking for in grading.