Things that are wrong

[inducer]

• Formulas/code: notation with pencil/paper vs. in a computer

  • Comments?

• Stronger connection between simulation and the math they know

  • Start slope-y/bend-y activities from rope pictures

• Connection between slope of line and slope of curve not well-developed

  • Slopes are ugly fractions (maybe OK)
  • Make it so that slopes are obviously different (65/7 = 37/13?)

• Tables: First human-generated, then machine-made

• Actually explain the code

  • Get rid of comment/mumbo-jumbo clutter (first time?)

• More manipulation of the code, sooner

• Stop-motion video of string on graph paper

• Function Legos (build a given shape out a formula)

  • But: don't want to be in f(x) formula mode too much

• [ ] Actually explain the code to Jana

cc @mstegeorge @kaushikcfd

[inducer]

Action items:

• [ ] Get a video with longer rope clamped down and under higher tension (Jana/George)
• [ ] Figure out web file upload (Kaushik)
• [ ] Make a way to produce tracing worksheet from rope on the web, with room for second differences (Andreas)
• [ ] Come up with descriptive/predictive discussion task, using worksheet (Jana/George)
• [ ] Come up with student-driven way of using the computer to fill the worksheet table (Andreas/Kaushik)
• [ ] Develop how we can convince the students that second differences (everybody)
• [ ] Base the activity on an (x,t) table, bendiness both ways (Andreas/Kaushik)
• [ ] Think of a way to turn computational rope finding into an activity (Andreas/Kaushik)