User Tools

Site Tools


cs601r_w2020:lab2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cs601r_w2020:lab2 [2020/01/10 17:50]
wingated
cs601r_w2020:lab2 [2021/06/30 23:42] (current)
Line 13: Line 13:
 Your notebook will be graded on the following: Your notebook will be graded on the following:
  
-  * 40% Part 1: Clearly displayed 10 bars+  * 35% Part 1: Clearly displayed 10 bars (one for baseline, one for each tweak independently)  
 +  * 5%  Part 1: Small writeup of conclusions from independent tweaks
   * 25% Part 2: Clear explanation of your tweaking strategy   * 25% Part 2: Clear explanation of your tweaking strategy
   * 25% Part 2: Actually run your tweaking strategy and show the results   * 25% Part 2: Actually run your tweaking strategy and show the results
   * 10% Tidy and legible figures, including labeled axes where appropriate   * 10% Tidy and legible figures, including labeled axes where appropriate
 +  * 10% Extra credit - Error bars on your figure in Part 1.
  
 ---- ----
Line 27: Line 29:
 For this lab, you will explore various tweaks to the basic classifier you coded in lab 1. There are two parts to the lab. For this lab, you will explore various tweaks to the basic classifier you coded in lab 1. There are two parts to the lab.
  
 +----
 ====Part 1==== ====Part 1====
  
 You must clearly show the individual effect of each tweak compared to the baseline. ​ For this part, you should present a simple bar chart (or possibly two or more, depending on your layout), clearly labeled with the baseline performance,​ and then the performance of each tweak relative to baseline. ​ You may plot absolute or relative performances;​ whichever is clearer. You must clearly show the individual effect of each tweak compared to the baseline. ​ For this part, you should present a simple bar chart (or possibly two or more, depending on your layout), clearly labeled with the baseline performance,​ and then the performance of each tweak relative to baseline. ​ You may plot absolute or relative performances;​ whichever is clearer.
  
-**Note:** I am not requiring error bars for this lab, although if we were doing this for real, they would be absolutely essential!+You must include a few sentences describing what you can conclude from evaluating all of these tweaks.
  
 +**Note:** I am not requiring error bars for this lab, because they are computationally intensive. ​ I have made them extra credit -- although if we were doing this for real, they would be absolutely required!
 +
 +----
 ====Part 2==== ====Part 2====
  
Line 41: Line 47:
 Note that you will not be graded on absolute performance of any run; what is important is thinking clearly through which tweaks make a difference. Note that you will not be graded on absolute performance of any run; what is important is thinking clearly through which tweaks make a difference.
  
 +----
 ====The Tweaks==== ====The Tweaks====
  
Line 57: Line 64:
  
 Some of these tweaks require additional parameters. ​ You should either leave them at their default values, or think of some reasonable way to set them.  Some of these tweaks require additional parameters. ​ You should either leave them at their default values, or think of some reasonable way to set them. 
 +
 +Note: pytorch does not (AFAIK) natively implement label smoothing. ​ In the interests of focusing on hyperparameter searching, **you may verbatim copy any internet code you like to help implement label smoothing.**
  
 ---- ----
-====Hints:====+====Hints====
  
 Activation functions and dropout can all be found in torch.nn Activation functions and dropout can all be found in torch.nn
Line 67: Line 76:
 This lab should be pretty straightforward,​ with the right script -- you should be able to iterate over tweaks and run your classifier in a tidy loop. Ideally, you'll code it up, let it run, and come back in a few hours to find the results! This lab should be pretty straightforward,​ with the right script -- you should be able to iterate over tweaks and run your classifier in a tidy loop. Ideally, you'll code it up, let it run, and come back in a few hours to find the results!
  
-If you find yourself cutting-and-pasting,​ you might want to rethink your strategy!+If you find yourself cutting-and-pasting,​ you might want to rethink your strategy.
  
  
cs601r_w2020/lab2.1578678628.txt.gz · Last modified: 2021/06/30 23:40 (external edit)