Difference between revisions of "Labs"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
See [[git|Using git and bitbucket]] for more information on your <span style="font-family:Courier;">''git''</span> repository from which you will be able to retrieve lab assignments and submit your solution code and reports. | See [[git|Using git and bitbucket]] for more information on your <span style="font-family:Courier;">''git''</span> repository from which you will be able to retrieve lab assignments and submit your solution code and reports. | ||
| − | The material that needs to be turned in for each lab will typically include code implementing the desired functionality for the lab, results that report on the outcome of running your code in different scenarios, and a hard-copy lab report that includes your code, results, and usually answers to a number of questions meant to verify your understanding of the material and the results. All this material needs to be committed and pushed to you git repository, and a hard copy of the lab report needs to be turned in at the beginning of the class when the lab is due. | + | The material that needs to be turned in for each lab will typically include code implementing the desired functionality for the lab, results that report on the outcome of running your code in different scenarios, and a hard-copy lab report that includes your code, results, and usually answers to a number of questions meant to verify your understanding of the material and the results. All this material needs to be committed and pushed to you <span style="font-family:Courier;">''git''</span> repository, and a hard copy of the lab report needs to be turned in at the beginning of the class when the lab is due. |
* [[Media:Lab1.pdf | Lab 1]] | * [[Media:Lab1.pdf | Lab 1]] | ||
Revision as of 19:59, 18 September 2017
See Using git and bitbucket for more information on your git repository from which you will be able to retrieve lab assignments and submit your solution code and reports.
The material that needs to be turned in for each lab will typically include code implementing the desired functionality for the lab, results that report on the outcome of running your code in different scenarios, and a hard-copy lab report that includes your code, results, and usually answers to a number of questions meant to verify your understanding of the material and the results. All this material needs to be committed and pushed to you git repository, and a hard copy of the lab report needs to be turned in at the beginning of the class when the lab is due.
