From WeBWorK
Jump to: navigation, search

Vectors in Problems: PG Code Snippet

This code snippet shows the essential PG code to use vectors in WeBWorK problems. Note that these are insertions, not a complete PG file. This code will have to be incorporated into the problem file on which you are working.

Problem Techniques Index

PG problem file Explanation

Initialization: Be sure to load and (since does not automatically load

## display vectors in ijk format
## Context()->flags->set( ijk=>1 );
## set the appearance of the ijk vectors
##    this sets them to be overset with
##    vector arrows, instead of boldface
# Context()->constants->set(
#   i => {TeX => "\mathit{\vec i}"},
#   j => {TeX => "\mathit{\vec j}"},
#   k => {TeX => "\mathit{\vec k}"},
# );

$v1 = Vector("<1,3>");
$v2 = Compute("<-3,1>");
$v3 = 3*i + 2*j - 4*k;
$v4 = Vector(1,1,0);

# create an array of the components of $v3
@v3comp = $v3->value;

$a = 3*i + j;
$b = $a + $v1;
$c = norm($v3);    # vector length   
$v5 = unit($v3);   # unit vector in same direction
$d = $v1 . $v2;    # dot product
$v6 = $v3 x $v4;      # cross product
$v3->isParallel($v4); # =1 if parallel, =0 if skew

Setup: We indicate that we are working in a vector context by setting the Context to be Vector. If we want to have vectors displayed, by default, as a sum of i,j,k components, we can set the ijk flag in the Context. This is commented out here; uncommenting it would result in the vector v1 here being shown as v1 = i + 3j instead of v1 = <1,3>, etc. Similarly, if we wanted to change the default display of the i, j and k vectors, say to have them display with overset arrows, we can redefine the TeX formatting of those constants, as shown in the second comment.

Then, we can define vectors as we might expect: either with the Vector or Compute constructors, or by using the predefined vector constants i, j and k.

Note that if we define the vector using the constants i, j and k, as in the definition of $v3 here, then the default display of that vector will be in i,j,k format even if we don't set the corresponding Context flag.

To explicitly require that the vectors be two-dimensional rather than three-dimensional, we would use Context('Vector2D') instead of Context('Vector').

The components of MathObjects vectors are available as an array from $v->value; thus, we could save the three components of the vector $v3 in the array @v3comp. Then, we can access the first component using $v3comp[0], the second component using $v3comp[1], etc. Better still, to get the first component of the vector $v3 we could use $v3->extract(1) instead of ($v3->value)[0]. (This appears only to be the case for vectors that are initially defined using angle-bracket notation, not for vectors that are defined using i, j, and k—and this behavior may be different for vectors of numbers and vectors of formulas.)

Enter the vector pointing from
\($a\) to \($b\):
\{ ans_rule(25) \}
Enter a vector perpendicular to this:
\{ ans_rule(25) \}
Enter a vector parallel to \($v3\):
\{ ans_rule(25) \}

Main text: We can then use the vectors that we created in the text section of the problem.

ANS( $v1->cmp() );

ANS( $v2->cmp( checker=>sub {
  my ($correct, $student, $ansHash) = @_;
  return $correct->isParallel($student);
}, showCoordinateHints => 0 ) );
## or:
# ANS( $v1->cmp( checker=>sub {
#   my ($correct, $student, $ansHash) = @_;
#   return $correct.$student == 0; } ) );
# make a custom answer checker as a subroutine
sub parallel_vector_cmp {
  my ($correct, $student, $ansHash) = @_;
  return $correct->isParallel($student);
ANS( $v3->cmp( checker=>~~&parallel_vector_cmp, 
               showCoordinateHints => 0 ) );

Answer evaluation: We can then use the vectors to check the answers that are given. Note that we have used custom answer checkers for the latter answer evaluators here, taking advantage of the built in dot product and isParallel method of vector objects. When checking if a student's vector is parallel to the correct vector, hints about which coordinates are incorrect can be misleading, so we set showCoordinateHints => 0.

Other properties of MathObjects vectors are given in the MathObjects reference table.

Problem Techniques Index

follow us