Difference between revisions of "SampleProblem4"

From WeBWorK_wiki
Jump to navigation Jump to search
("typeset version" link changed from rochester to maa to fix broken "show problem source" button)
(Fix some formatting issues, correct the solutions section, and touch up a few wordings. Add some comments to make it easier to identify the sections as you edit.)
Line 22: Line 22:
 
The sample file attached to this page shows this; below the file is shown to the left, with a second column on its right that explains the different parts of the problem that are indicated above.
 
The sample file attached to this page shows this; below the file is shown to the left, with a second column on its right that explains the different parts of the problem that are indicated above.
 
</p>
 
</p>
  +
 
<table cellspacing="0" cellpadding="2" border="0">
 
<table cellspacing="0" cellpadding="2" border="0">
 
<tr valign="top">
 
<tr valign="top">
<th> PG problem file </th>
+
<th>PG problem file</th>
<th> Explanation </th>
+
<th>Explanation</th>
 
</tr>
 
</tr>
  +
  +
<!--================ Tagging ================-->
  +
 
<tr valign="top">
 
<tr valign="top">
 
<td style="background-color:#ddddff;border:black 1px dashed;">
 
<td style="background-color:#ddddff;border:black 1px dashed;">
Line 51: Line 55:
 
</pre>
 
</pre>
 
</td>
 
</td>
  +
  +
<!--------------------------------------------->
  +
 
<td style="background-color:#ccccff; padding:7px;">
 
<td style="background-color:#ccccff; padding:7px;">
 
<p>
 
<p>
This is the <strong>tagging and description</strong> section of the problem. Note that any line that begins with a "#" character is a <em>comment</em> for other authors who read the problem, and is not interpreted by !WeBWorK.
+
This is the <strong>tagging and description</strong> section of the problem. Note that any line that begins with a <code>#</code> character is a <em>comment</em> for other authors who read the problem, and is not interpreted by WeBWorK.
 
</p>
 
</p>
 
<p>
 
<p>
Line 61: Line 68:
 
All of the tagging information exists to allow the problem to be easily indexed. Because this is a sample problem there isn't a textbook per se, and we've used some default tagging values. There is an on-line
 
All of the tagging information exists to allow the problem to be easily indexed. Because this is a sample problem there isn't a textbook per se, and we've used some default tagging values. There is an on-line
 
[http://hobbes.la.asu.edu/Holt/chaps-and-secs.html list of current chapter and section names] and a similar
 
[http://hobbes.la.asu.edu/Holt/chaps-and-secs.html list of current chapter and section names] and a similar
[http://hobbes.la.asu.edu/Holt/keywords.html list of keywords]. The list of keywords should be comma separated and quoted (e.g., KEYWORDS('calculus','derivatives')).
+
[http://hobbes.la.asu.edu/Holt/keywords.html list of keywords]. The list of keywords should be comma separated and quoted (e.g., <code>KEYWORDS('calculus','derivatives')</code>).
 
</p>
 
</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
  +
  +
<!--================ Initialization ================-->
  +
 
<tr valign="top">
 
<tr valign="top">
 
<td style="background-color:#ddffdd;border:black 1px dashed;">
 
<td style="background-color:#ddffdd;border:black 1px dashed;">
Line 77: Line 87:
 
</pre>
 
</pre>
 
</td>
 
</td>
  +
  +
<!--------------------------------------------->
  +
 
<td style="background-color:#ccffcc;padding:7px;">
 
<td style="background-color:#ccffcc;padding:7px;">
 
<p>
 
<p>
Line 83: Line 96:
 
<p>
 
<p>
 
The <code>loadMacros</code> command loads information that works behind the scenes. We load the <code>PGML.pl</code> file to load the PGML formatting
 
The <code>loadMacros</code> command loads information that works behind the scenes. We load the <code>PGML.pl</code> file to load the PGML formatting
commands (similar to markDown) and the <code>PGcourse.pl<code> file to provide any local course customizations. The<code> PGcourse.pl</code> file is usually placed in the courses <code>templates/macros</code> directory
+
commands (similar to markDown) and the <code>PGcourse.pl</code> file to provide any local course customizations. The <code>PGcourse.pl</code> file is usually placed in the course's <code>templates/macros</code> directory
 
</p>
 
</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
  +
  +
<!--================ Set Up ================-->
  +
 
<tr valign="top">
 
<tr valign="top">
 
<td style="background-color:#ffffdd;border:black 1px dashed;">
 
<td style="background-color:#ffffdd;border:black 1px dashed;">
Line 96: Line 112:
 
</pre>
 
</pre>
 
</td>
 
</td>
  +
  +
<!--------------------------------------------->
  +
 
<td style="background-color:#ffffcc;padding:7px;">
 
<td style="background-color:#ffffcc;padding:7px;">
 
<p>
 
<p>
This is the <strong>problem set-up section</strong> of the problem. <code>Context("Numeric");</code> sets the "context", which determines how variables are interpreted. Contexts and context explanations are given on [[ContextList|this help page]]. Setting <code>showpartialCorrectAnswers</code> to 1 means that feedback as to which sub-questions have been correctly answered in the problem, otherwise the feedback indicates that there is a wrong answer somewhere. (Use the latter mode for multiple choice or true false questions.)
+
This is the <strong>problem set-up section</strong> of the problem. <code>Context("Numeric");</code> sets the "context", which determines how variables are interpreted. Contexts and context explanations are given on [[ContextList|this help page]]. Setting <code>showpartialCorrectAnswers</code> to 1 means that feedback as to which sub-questions have been correctly answered in the problem will be given, otherwise the feedback indicates that there is a wrong answer somewhere. (Use the latter mode for multiple choice or true/false questions.)
 
</p>
 
</p>
 
<p>
 
<p>
The bulk of the set-up section defines variables that we use in the rest of the problem. All <em>scalar variables</em> are prefaced with a dollar sign: thus <code>$a</code> is a variable that has a (non-vector, non-array) value. </code>.
+
The bulk of the set-up section defines variables that we use in the rest of the problem. All <em>scalar variables</em> are prefaced with a dollar sign: thus <code>$a</code> is a variable that has a (non-array, non-associative-array) value.
 
</p>
 
</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
  +
  +
<!--================ Text ================-->
  +
 
<tr valign="top">
 
<tr valign="top">
 
<td style="background-color:#ffdddd;border:black 1px dashed;">
 
<td style="background-color:#ffdddd;border:black 1px dashed;">
Line 113: Line 135:
 
The number twelve is [_______]{12}
 
The number twelve is [_______]{12}
 
Type the formula [`1+\frac{x}{2}`] [__________]{"1+x/2"}
 
Type the formula [`1+\frac{x}{2}`] [__________]{"1+x/2"}
 
   
 
Twelve is [______]{Real(12)}
 
Twelve is [______]{Real(12)}
Line 124: Line 145:
   
 
</pre>
 
</pre>
  +
</td>
  +
  +
<!--------------------------------------------->
  +
 
<td style="background-color:#ffcccc;padding:7px;">
 
<td style="background-color:#ffcccc;padding:7px;">
 
<p>
 
<p>
Line 130: Line 155:
 
<code>BEGIN_PGML</code> and <code>END_PGML</code> replace the <code>BEGIN_TEXT/END_TEXT</code> structure used in the other template samples.
 
<code>BEGIN_PGML</code> and <code>END_PGML</code> replace the <code>BEGIN_TEXT/END_TEXT</code> structure used in the other template samples.
 
The <code>Context()-&gt;texStrings</code> line is not needed. (If you are not using the latest version of pg you may need to replace <code>BEGIN_PGML</code> with its expanded version <code>TEXT(PGML::Format2(<<'END_PGML'));</code>
 
The <code>Context()-&gt;texStrings</code> line is not needed. (If you are not using the latest version of pg you may need to replace <code>BEGIN_PGML</code> with its expanded version <code>TEXT(PGML::Format2(<<'END_PGML'));</code>
which is
 
  +
which is given here as a comment that you can uncomment.
 
</p>
 
</p>
 
<p>
 
<p>
 
Answer blanks are indicated by <code>[______]</code> where the number of blanks indicates the width of the answer blank. The correct answer can be given
 
Answer blanks are indicated by <code>[______]</code> where the number of blanks indicates the width of the answer blank. The correct answer can be given
in curly braces immediately afterward <code>{"1+x/2"}</code>. TeX formulas can be entered as <code> [``1+\frac{x}{2}``] </code> or in calculator
+
in curly braces immediately afterward <code>{"1+x/2"}</code>. TeX formulas within the text of the problem can be entered as <code>[``1+\frac{x}{2}``]</code> or in calculator
notation as <code>[:1+x/2:} </code> <code>[`[$f]`] </code> typesets the formula $f in inline math mode.
+
notation as <code>[:1+x/2:]</code>. A variable substitution would be given as <code>[$a]</code>, whicle <code>[`[$f]`] </code> typesets the formula for $f in inline math mode.
 
</p>
 
</p>
 
<p>
 
<p>
A link to an interactive online calculator and to several dozens examples of using PGML is on the''' [[PGLabs]] ''' page.
+
A link to an interactive online test framework and to several dozens examples of using PGML is on the''' [[PGLabs]] ''' page.
Here is the [https://courses.webwork.maa.org/webwork2/cervone_course/PGML-examples/4?login_practice_user=true typeset version] of this sample problem
+
Here is the [https://courses.webwork.maa.org/webwork2/cervone_course/PGML-examples/4?login_practice_user=true active version] of this sample problem.
 
</p>
 
</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
  +
  +
<!--================ Answers ================-->
  +
 
<tr valign="top">
 
<tr valign="top">
 
<td style="background-color:#eeddff;border:black 1px dashed;">
 
<td style="background-color:#eeddff;border:black 1px dashed;">
 
<pre>
 
<pre>
 
BEGIN_PGML_SOLUTION
 
BEGIN_PGML_SOLUTION
$PAR SOLUTION $PAR
+
*SOLUTION*
   
 
You can use PGML in your solution if you use the structure
 
You can use PGML in your solution if you use the structure
 
above. There is currently no short cut.
 
above. There is currently no short cut.
 
END_PGML_SOLUTION
 
END_PGML_SOLUTION
Context()-&gt;normalStrings;
 
   
 
ENDDOCUMENT();
 
ENDDOCUMENT();
 
</pre>
 
</pre>
  +
</td>
  +
  +
<!--------------------------------------------->
  +
 
<td style="background-color:#eeccff;padding:7px;">
 
<td style="background-color:#eeccff;padding:7px;">
 
<p>
 
<p>
This is the <strong>answer and solution</strong> section of the problem. The answers were given along side the problems using
+
This is the <strong>answer and solution</strong> section of the problem. Since the answers were given along side the problems when you use
PGML so the answer section is not needed although it is allowed.
+
PGML, the answer section is not needed, although it is allowed.
 
</p>
 
</p>
 
<p>
 
<p>
Then, we explain the solution to the student. Currently there is no short cut for using PGML in the solution section, but one can use the long version as above.
+
Then, we explain the solution to the student. You can use <code>BEGIN_PGML_SOLUTION/END_PGML_SOLUTION</code> just as you wold
  +
<code>BEGIN_SOLUTION/END_SOLUTION</code>. There is also <code>BEGIN_PGML_HINT/END_PGML_HINT</code> for providing a hit to the student.
 
</p>
 
</p>
 
<p>
 
<p>
Line 169: Line 200:
 
</td>
 
</td>
 
</tr>
 
</tr>
  +
  +
<!--================================-->
  +
 
</table>
 
</table>
   

Revision as of 14:13, 20 July 2012

A PGML WeBWorK Sample Problem

This sample problem illustrates the basics of how to use PGML commands to layout a question.

This sample just scratches the surface of what is possible using these mark up commands. Page through the sample questions to see what can be done and click on the "show problem source" button to see how to accomplish it.

As usual a standard WeBWorK PG file has five sections:

  1. A tagging and description section, that describes the problem for future users and authors,
  2. An initialization section, that loads required macros for the problem,
  3. A problem set-up section that sets variables specific to the problem,
  4. A text section, that gives the text that is shown to the student, and
  5. OPTIONAL --An answer , that specifies how the answer(s) to the problem is(are) marked for correctness, and gives a solution that may be shown to the student after the problem set is complete. As you will see this section can be used but are not necessary when using PGML commands.
  6. A solution section

The sample file attached to this page shows this; below the file is shown to the left, with a second column on its right that explains the different parts of the problem that are indicated above.

PG problem file Explanation
# DESCRIPTION
# A simple sample problem that asks students to 
# differentiate a trigonometric function.
# WeBWorK problem written by Gavin LaRose
# <glarose(at)umich(dot)edu>
# and modified by Mike Gage   gage(at)math(dot)rochester(dot)edu
# ENDDESCRIPTION

## DBsubject('WeBWorK')
## DBchapter('Demos')
## DBsection('Problem')
## KEYWORDS('')
## TitleText1('')
## EditionText1('')
## AuthorText1('')
## Section1('')
## Problem1('')
## Author('Gavin LaRose')
## Institution('UMich')

This is the tagging and description section of the problem. Note that any line that begins with a # character is a comment for other authors who read the problem, and is not interpreted by WeBWorK.

The description is provided to give a quick summary of the problem so that someone reading it later knows what it does without having to read through all of the problem code.

All of the tagging information exists to allow the problem to be easily indexed. Because this is a sample problem there isn't a textbook per se, and we've used some default tagging values. There is an on-line list of current chapter and section names and a similar list of keywords. The list of keywords should be comma separated and quoted (e.g., KEYWORDS('calculus','derivatives')).

DOCUMENT();
loadMacros(
"PGstandard.pl",
"PGML.pl",
"MathObjects.pl",
"PGcourse.pl",
);

This is the initialization section of the problem. The first executed line of the problem must be the DOCUMENT(); command. Note that every command must end with a semicolon.

The loadMacros command loads information that works behind the scenes. We load the PGML.pl file to load the PGML formatting commands (similar to markDown) and the PGcourse.pl file to provide any local course customizations. The PGcourse.pl file is usually placed in the course's templates/macros directory

# make sure we're in the context we want
Context("Numeric");
$showPartialCorrectAnswers = 1;
$f = Formula("cos^2(x)+sin^2(x)");

This is the problem set-up section of the problem. Context("Numeric"); sets the "context", which determines how variables are interpreted. Contexts and context explanations are given on this help page. Setting showpartialCorrectAnswers to 1 means that feedback as to which sub-questions have been correctly answered in the problem will be given, otherwise the feedback indicates that there is a wrong answer somewhere. (Use the latter mode for multiple choice or true/false questions.)

The bulk of the set-up section defines variables that we use in the rest of the problem. All scalar variables are prefaced with a dollar sign: thus $a is a variable that has a (non-array, non-associative-array) value.

TEXT(beginproblem());
#TEXT(PGML::Format2(<<'END_PGML'));
BEGIN_PGML
The number twelve is [_______]{12}  
Type the  formula [`1+\frac{x}{2}`] [__________]{"1+x/2"}

Twelve is [______]{Real(12)}  
2 mod 10 is [______]{Real(2)->with(period=>10)}
[`[$f]`] is equal to [_______]{Real(1)}
Twelve is [______]{num_cmp(12)}

The number 12 is [____]{answer=>12,width=>10}
END_PGML

This is the text section of the problem. The TEXT(beginproblem()); line displays a header for the problem. Everything between the BEGIN_PGML and END_PGML lines (each of which must appear alone on a line) is shown to the student. BEGIN_PGML and END_PGML replace the BEGIN_TEXT/END_TEXT structure used in the other template samples. The Context()->texStrings line is not needed. (If you are not using the latest version of pg you may need to replace BEGIN_PGML with its expanded version TEXT(PGML::Format2(<<'END_PGML')); which is given here as a comment that you can uncomment.

Answer blanks are indicated by [______] where the number of blanks indicates the width of the answer blank. The correct answer can be given in curly braces immediately afterward {"1+x/2"}. TeX formulas within the text of the problem can be entered as [``1+\frac{x}{2}``] or in calculator notation as [:1+x/2:]. A variable substitution would be given as [$a], whicle [`[$f]`] typesets the formula for $f in inline math mode.

A link to an interactive online test framework and to several dozens examples of using PGML is on the PGLabs page. Here is the active version of this sample problem.

BEGIN_PGML_SOLUTION
*SOLUTION*

You can use PGML in your solution if you use the structure
above.  There is currently no short cut.
END_PGML_SOLUTION

ENDDOCUMENT();

This is the answer and solution section of the problem. Since the answers were given along side the problems when you use PGML, the answer section is not needed, although it is allowed.

Then, we explain the solution to the student. You can use BEGIN_PGML_SOLUTION/END_PGML_SOLUTION just as you wold BEGIN_SOLUTION/END_SOLUTION. There is also BEGIN_PGML_HINT/END_PGML_HINT for providing a hit to the student.

The ENDDOCUMENT(); command is the last command in the file.