Skip to content

Reorganizing/Merging of Some Linear Algebra Lessons (MX2, MX3, and change of basis/GT5) #780

@jkostiuk

Description

@jkostiuk

I'd like to pitch a suggestion for re-organizing some content in Linear Algebra--original conversation started in #776

Context: Section GT5 of the activity book is change-of-basis. The file is in the main project, but I don't believe it's published as part of the main edition yet. My instructors and I taught with this in Fall and Spring and the lesson itself went well for us. Now that we're thinking about including this in the main edition, we want to take a step back and make sure the lesson is in the right place and that the other lessons around it flow.

My specific suggestions for reorganizing:

  1. merge MX3 into MX2. Given the way we defined the inverse and inverse matrix, I think it follows naturally in that lesson that we can use the inverse matrix to solve a system of equations. then, in the MX2 checkit, we can have task 1 be "explain why this matrix isn't invertible" task 2 can be your reworked "find the inverse" and then we can add a short task 3 that's "use your inverse to solve the system". While this makes MX2 a little longer, the ideas are well-connected: we defined the inverse matrix/trafo to be "the unique solution to this equation" so it would make thematic sense for the lesson to end with "now we can easily compute this unique solution".
  2. Then, GT5 becomes a new MX3.
  3. If we do this, then I think we can add 2-3 activities to GT4 to do some version of diagonalization (i.e., after computing a basis of eigenvectors, use that to diagonalize a matrix).

What does the community think? (Note that change-of-basis cannot happen earlier than this suggestion without significant edits because it requires the matrix inverse).

Tagging some specific people, but all comments welcome here!
@siwelwerd @StevenClontz @jford1906 @jbunn3 @megancl13

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions