Difference between revisions of "Labs"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''FAIR WARNING:''' Although solutions to the labs are not distributed, solutions from students who previously took the course may be available on the Internet. Using those solutions is the safest way to earn an '''F''' in the course, as it represents a blatant violation of | '''FAIR WARNING:''' Although solutions to the labs are not distributed, solutions from students who previously took the course may be available on the Internet. Using those solutions is the safest way to earn an '''F''' in the course, as it represents a blatant violation of | ||
| − | the [https://engineering.wustl.edu/current-students/student-services/Pages/academic-integrity-policy.aspx student's Code of Academic Integrity]. In addition, not all those solutions may be correct | + | the [https://engineering.wustl.edu/current-students/student-services/Pages/academic-integrity-policy.aspx student's Code of Academic Integrity]. In addition, not all those solutions may be correct and furthermore minor changes are introduced each year, so that in addition to relying on [https://theory.stanford.edu/~aiken/moss/ MOSS] to spot code similarities, those offer easy flags for catching instances of plagiarism. |
See [[git|Using <span style="font-family:Courier;">''git''</span> and <span style="font-family:Courier;">''bitbucket''</span>]] 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 <span style="font-family:Courier;">''git''</span> and <span style="font-family:Courier;">''bitbucket''</span>]] 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. | ||
| Line 6: | Line 6: | ||
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. | 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. | ||
| − | * [https://www.dropbox.com/s/ | + | * [https://www.dropbox.com/s/kr7nhtyr90yq31o/lab1.docx?dl=0 Lab1] and [https://www.dropbox.com/s/fi5scaku4k6lgoo/lab1report.docx?dl=0 Lab1 report] |
| − | ** [https://www.dropbox.com/s/ | + | ** [https://www.dropbox.com/s/36n0b5y7w2xvg2c/lab1_2015_notes.pdf?dl=0 Feedback on Lab1 from 2015] |
| − | ** [https://www.dropbox.com/s/ | + | ** [https://www.dropbox.com/s/0c5aggqexrfz3j5/Feedback_on_Lab1_2014.docx?dl=0 Feedback on Lab1 from 2014] |
| − | * [https://www.dropbox.com/s/ | + | * [https://www.dropbox.com/s/gtwsearoczq37u5/lab2.docx?dl=0 Lab2] and [https://www.dropbox.com/s/cye90abglhgz3tu/lab2report.docx?dl=0 Lab2 report] |
| − | ** [https://www.dropbox.com/s/ | + | ** [https://www.dropbox.com/s/22wbowgku9wbhm0/Using_a_Remote_Linux_Desktop_to_Access_ONL.docx?dl=0 Using a Remote Linux Desktop (to Access ONL)] |
| − | * [https://www.dropbox.com/s/ | + | * [https://www.dropbox.com/s/z1rq63cpgryj1t3/lab3.docx?dl=0 Lab3] and [https://www.dropbox.com/s/zi9i7mjluxxnq0c/lab3report.docx?dl=0 Lab3 report] |
| − | * [https://www.dropbox.com/s/ | + | * [https://www.dropbox.com/s/4opis0t7l7husow/lab4.docx?dl=0 Lab4] and [https://www.dropbox.com/s/6veyip2zdcbvjk7/lab4report.docx?dl=0 Lab4 report] |
| − | * [https://www.dropbox.com/s/ | + | * [https://www.dropbox.com/s/c25o072rqes1w00/lab5.docx?dl=0 Lab5] and [https://www.dropbox.com/s/heghd1llmy3svi0/lab5report.docx?dl=0 Lab5 report] |
| − | * [https://www.dropbox.com/s/ | + | * [https://www.dropbox.com/s/wrfrwfsp3qz3jlv/lab6.docx?dl=0 Lab6] and [https://www.dropbox.com/s/sidk3octxcytxq4/lab6report.docx?dl=0 Lab6 report] |
| + | |||
| + | The first lab must be completed individually by each student, but subsequent labs can be done in '''teams of two'''. This is actually strongly encouraged as labs 3 and 5 are rather long, and can be a lot of work if you are doing them just by yourself. A team only needs to turn in one lab assignment, and unless warranted by exceptional conditions, both team partners receive the same grade. If you decide to work with a partner, you need to record your team by '''Monday September 9, 2019, before 5:00pm CT'''. To record your team, send an email to the instructor with the names and student IDs of both partners, and make sure the two partners are copied on the email.<br/> | ||
| + | If you want to change your mind for a subsequent lab, ''i.e.,'' you did not have a partner and now want to have one, or conversely had a partner but now want to complete the lab on your own or switch partner, '''you MUST notify both the instructor and your previous and new partners (when applicable)''' of your decision. This needs to be done in a timely fashion, ''i.e.,'' '''less than 3 days after the new lab has been assigned''', by sending a notification email to the instructor and previous and new partners, as applicable.<br/> | ||
Latest revision as of 11:40, 27 August 2019
FAIR WARNING: Although solutions to the labs are not distributed, solutions from students who previously took the course may be available on the Internet. Using those solutions is the safest way to earn an F in the course, as it represents a blatant violation of the student's Code of Academic Integrity. In addition, not all those solutions may be correct and furthermore minor changes are introduced each year, so that in addition to relying on MOSS to spot code similarities, those offer easy flags for catching instances of plagiarism.
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.
- Lab1 and Lab1 report
- Lab2 and Lab2 report
- Lab3 and Lab3 report
- Lab4 and Lab4 report
- Lab5 and Lab5 report
- Lab6 and Lab6 report
The first lab must be completed individually by each student, but subsequent labs can be done in teams of two. This is actually strongly encouraged as labs 3 and 5 are rather long, and can be a lot of work if you are doing them just by yourself. A team only needs to turn in one lab assignment, and unless warranted by exceptional conditions, both team partners receive the same grade. If you decide to work with a partner, you need to record your team by Monday September 9, 2019, before 5:00pm CT. To record your team, send an email to the instructor with the names and student IDs of both partners, and make sure the two partners are copied on the email.
If you want to change your mind for a subsequent lab, i.e., you did not have a partner and now want to have one, or conversely had a partner but now want to complete the lab on your own or switch partner, you MUST notify both the instructor and your previous and new partners (when applicable) of your decision. This needs to be done in a timely fashion, i.e., less than 3 days after the new lab has been assigned, by sending a notification email to the instructor and previous and new partners, as applicable.
