Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| 184_notes:comp_process [2022/04/20 15:51] – [Predictions and Evaluations] woodsna1 | 184_notes:comp_process [2022/04/20 15:55] (current) – [Logistics] woodsna1 | ||
|---|---|---|---|
| Line 35: | Line 35: | ||
| When your team has completed the program, assess how closely it matches your predictions. Are there errors in your prediction? In the coded model? Think through ways that the coded model could more closely reflect reality, and any improvements that your team can add. | When your team has completed the program, assess how closely it matches your predictions. Are there errors in your prediction? In the coded model? Think through ways that the coded model could more closely reflect reality, and any improvements that your team can add. | ||
| ===== Logistics ===== | ===== Logistics ===== | ||
| + | An easy way to get very lost as a group is having each person looking at a separate computer screen with their own version of the code. Instead, pick a single person to type the code with input from all other group members. Choosing a coder with less programming experience will make sure that your entire group stays together. If you are a CS/ | ||
| + | In class, one of the best ways to keep everybody on the same page is starting a zoom meeting, having each team member log in on their own device, and having the coder share their screen with the program up. Then you'll each be able to see what's going on without huddling around one small screen. | ||