Editing USub Applet Sample Problem

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 3: Line 3:
 
<h2>Sample Problem with uSub.swf embedded</h2>
 
<h2>Sample Problem with uSub.swf embedded</h2>
 
<p style="background-color:#eeeeee;border:black solid 1px;padding:3px;">
 
<p style="background-color:#eeeeee;border:black solid 1px;padding:3px;">
<em>This sample problem shows how to use the u-substitution applet.</em>
+
<em>This sample problem shows how to use this versatile applet.</em>
 
</p>
 
</p>
<p style="background-color:#93BED2;border:black solid 1px;padding:3px;">This applet and WeBWorK problem are based upon work supported by the National Science Foundation under Grant Number DUE-0941388.</p>
 
<p style="background-color:#ffccff;border:black solid 1px;padding:3px;">Click here to see a problem like this in action: [https://testcourses.webwork.maa.org/webwork2/FlashAppletDemos/variousAppletProblems/23/?user=practice1&effectiveUser=practice1&key=GR2uPvmajnoZz2cVTtrdBXsMFiO2C4k7&displayMode=MathJax&showOldAnswers=0 testcourses.webwork.maa.org/webwork2/FlashAppletDemos]</p>
 
 
<p>
 
<p>
[[File:USub.jpg]]
 
<br>
 
 
A standard WeBWorK PG file with an embedded applet has six sections:
 
A standard WeBWorK PG file with an embedded applet has six sections:
 
</p>
 
</p>
Line 21: Line 17:
 
</ol>
 
</ol>
 
<p>
 
<p>
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. A screenshot of the applet embedded in this WeBWorK problem is shown above.<br>
+
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. A screenshot of the applet embedded in this WeBWorK problem is shown below:<br>
+
[[File:USub.jpg]]
Other applet sample problems: <br>
+
<br>
[[GraphLimit Flash Applet Sample Problem]]<br>[[GraphLimit Flash Applet Sample Problem 2]]<br>[[Derivative Graph Matching Flash Applet Sample Problem]]<br>
+
Other applet sample problems: [[GraphLimit Flash Applet Sample Problem]]<br>[[GraphLimit Flash Applet Sample Problem 2]]<br>[[Derivative Graph Matching Flash Applet Sample Problem]]
[[Hint Applet (Trigonometric Substitution) Sample Problem]]
 
 
</p>
 
</p>
 
  +
<table cellspacing="0" cellpadding="2" border="0">
{| style=" background-color:#ffffff;" cellpadding="5" cellspacing="0" border="1"
 
  +
<tr valign="top">
! scope="col" width="50%"| PG problem file
+
<th> PG problem file </th>
! scope="col" width="50%"| Explanation
+
<th> Explanation </th>
|- style=" background-color:#ddddff;"
+
</tr>
| <pre>
+
<tr valign="top">
  +
<td style="background-color:#ddddff;border:black 1px dashed;">
  +
<pre>
 
##DESCRIPTION
 
##DESCRIPTION
 
## Integration with substitution
 
## Integration with substitution
Line 49: Line 45:
 
## Section1('')
 
## Section1('')
 
## Problem1('')
 
## Problem1('')
########################################
+
########################################################################
# This work is supported in part by the
+
# This work is supported in part by the National Science Foundation
# National Science Foundation
 
 
# under the grant DUE-0941388.
 
# under the grant DUE-0941388.
########################################
+
########################################################################
 
</pre>
 
</pre>
| <p>
+
</td>
  +
<td style="background-color:#ccccff; padding:7px;">
  +
<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 "#" character is a <em>comment</em> for other authors who read the problem, and is not interpreted by WeBWorK.
 
</p>
 
</p>
Line 65: Line 61:
 
[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., KEYWORDS('calculus','derivatives')).
 
</p>
 
</p>
|- style="background-color:#ddffdd;"
 
  +
</td>
| <pre>
+
</tr>
DOCUMENT();
+
<tr valign="top">
  +
<td style="background-color:#ddffdd;border:black 1px dashed;">
  +
<pre>
  +
DOCUMENT(); # This should be the first executable line in the problem.
   
 
loadMacros(
 
loadMacros(
Line 75: Line 71:
 
);
 
);
 
</pre>
 
</pre>
| <p>
+
</td>
  +
<td style="background-color:#ccffcc;padding:7px;">
  +
<p>
 
This is the <strong>initialization section</strong> of the problem. The first executed line of the problem <strong>must</strong> be the <code>DOCUMENT();</code> command. Note that every command <em>must end with a semicolon</em>.
 
This is the <strong>initialization section</strong> of the problem. The first executed line of the problem <strong>must</strong> be the <code>DOCUMENT();</code> command. Note that every command <em>must end with a semicolon</em>.
 
</p>
 
</p>
Line 81: Line 77:
 
The <code>loadMacros</code> command loads information that works behind the scenes. For our purposes we can usually just load the macros shown here and not worry about things further.
 
The <code>loadMacros</code> command loads information that works behind the scenes. For our purposes we can usually just load the macros shown here and not worry about things further.
 
</p>
 
</p>
|- style="background-color:#ffffdd;"
 
  +
</td>
| <pre>
+
</tr>
  +
<tr valign="top">
  +
<td style="background-color:#ffffdd;border:black 1px dashed;">
  +
<pre>
 
# Set up problem
 
# Set up problem
 
TEXT(beginproblem());
 
TEXT(beginproblem());
 
$showPartialCorrectAnswers = 1;
 
$showPartialCorrectAnswers = 1;
 
Context("Numeric");
 
Context("Numeric");
Context()->variables->add(u=>"Real");
 
   
$b = random(1,2,1);
 
  +
$qtype='first_derivative';
$ubig = Compute("$b+$b^2")+random(1,2,1);
 
$vbig = Compute("2+2*($b+$b^2)");
 
$vsmall = -$vbig;
 
   
$anslist = List(
 
  +
$showHint = 0;
Compute("cos(u)"),
 
  +
if(time>$dueDate){
Compute("0"),
 
  +
$showHint=1;
Compute("$b+$b^2"),
 
  +
}
Compute("sin($b+$b^2)"));
 
   
  +
$x1=random(-8,-2,1);
  +
$x2=$x1+random(2,4,1);
  +
$x3=$x2+random(2,3,1);
  +
$x4=random($x3+2,7,1);
 
</pre>
 
</pre>
| <p>
+
</td>
  +
<td style="background-color:#ffffcc;padding:7px;">
  +
<p>
 
This is the <strong>problem set-up section</strong> of the problem.
 
This is the <strong>problem set-up section</strong> of the problem.
 
</p>
 
</p>
 
<p>
 
<p>
The uSub.swf applet has the student enter a four part solution: the integrand after the u-substitution, the lower limit of integration in terms of u, the upper limit of integration in terms of u, and the value of the integral. The correct answer must be entered in list format in the pg file. That is what the code <code>$anslist = List(Compute("cos(u)"),</code> <code>Compute("0"),</code><code>Compute("$b+$b^2"),</code> <code>Compute("sin($b+$b^2)"));</code> does. The line <code>Context()->variables->add(u=>"Real");</code> adds the variable u to the context. <code>$vbig</code> and <code>$vsmall</code> are the vertical axes graph window settings. These can be different for the two graphs, but this is generally not a good idea as the purpose of the applet is to show the student that after a u-substitution, the are of the integrand will be the same even though the shape of the graph may change. Functions must be carefully chosen to convey this message and so that the two graph windows can be the same size. <code>$ubig</code> is the maximum value of the horizontal graph window for both graphs. The minimum value for this problem is coded in the pg file to '-3'. This is not necessary, it can be set to any value smaller than the maximum horizontal window value.
 
  +
The GraphLimits.swf applet will accept four different question types, specified with the <code>$qtype</code> variable. These are: limits, continuity, first_derivative and second_derivative. This sample problem is set to 'first_derivative'.
 
</p>
 
</p>
|- style="background-color:#ccffff;"
 
  +
<p>
| <pre>
 
  +
The applet has solution/hint information embedded in it. When <code>$hintState=0</code>, this information is not shown. When <code>$hintState=1</code>, this information is revealed. The <code>time</code> parameter tracks the current date and time. The conditional compares that to the due date for the problem set (in the <code>$dueDate</code> scalar variable) and sets <code>$hintState</code> to 1 if the due date has passed and leaves <code>$hintState</code> set to 0 if the assignment is not yet due.
###################################
 
  +
</p>
# Create link to applet
 
  +
<p>
###################################
 
  +
The four variables <code>$x1</code>, <code>$x2</code>, <code>$x3</code> and <code>$x4</code> are the x-coordinates of four points on the graph that the applet will set to be a removable discontinuity, a jump discontinuity or a cusp. The order of these phenomena is random as are the y-values chosen. The x-coordinates must be between -10 and 10.
$appletName = "uSub";
 
  +
</p>
$applet = FlashApplet(
 
  +
</td>
codebase
 
  +
</tr>
=> findAppletCodebase("$appletName.swf"),
 
  +
<tr valign="top">
appletName => $appletName,
 
  +
<td style="background-color:#ccffff;border:black 1px dashed;">
appletId => $appletName,
 
  +
<pre>
setStateAlias => 'setXML',
 
  +
##########################################################################
getStateAlias => 'getXML',
 
  +
# How to use the Graph_Test applet.
setConfigAlias => 'setConfig',
 
  +
# Purpose: The purpose of this applet is to ask graphical limit questions
maxInitializationAttempts => 5,
 
  +
# Use of applet: The applet state consists of the following fields:
answerBoxAlias => 'answerBox',
 
  +
# qType - question type: limits, continuity, first_derivative,
height => '550',
 
  +
# second_derivative
width => '700',
 
  +
# hintState - context sensitive help is either on or off.
bgcolor => '#e8e8e8',
 
  +
# Generally turned on after dueDate
debugMode => 0,
 
  +
# problemSeed - the seed sets the random parameters that control which
submitActionScript =>
 
  +
# graph is chosen. If the seed is changed, the graph is changed.
qq{getQE("answerBox").value
 
  +
##########################################################################
=getApplet("$appletName").getAnswer() },
 
  +
# qType = first_derivative
  +
# get_interval_info - given a type of interval returns a list of intervals
  +
# with that characteristic
  +
# Valid types are - increasing, decreasing, constant, up, down, straight
  +
# up, down and straight pertain to the concavity of the function on the
  +
# interval
  +
# sample function call: get_interval_info("increasing")
  +
# describe_interval - given an interval and a type, the function returns
  +
# information about the interval.
  +
# Valid types are -
  +
# updown (for concavity information),
  +
# posneg1 (for sign of first derivative),
  +
# posneg2 (for sign of second derviative),
  +
# incdec (for whether function is increasing or decreasing on the
  +
# interval.
  +
# sample function call: describe_interval($x1,$x2,"updown")
  +
# right_limits - returns a list of points (a,b) such that
  +
# lim_{x\to a^-}f(x)=b, but lim_{x\to a^+}f(x)\= b
  +
# left_limits - returns a list of points (a,b) such that
  +
# lim_{x\to a^+}f(x)=b, but lim_{x\to a^-}f(x)\= b
  +
# neither_limits - returns a list of points (a,b) such that
  +
# lim_{x\to a^-}f(x)\=lim_{x\to a^+}f(x)\= f(a)=b
  +
# get_intervals returns a list of intervals on which f(x) is continuous.
  +
# get_f_of_x - given x value, returns f(x).
  +
# returns NaN for x notin [-10,10].
  +
# getf_list - given x value and string returns
  +
# "function" - returns f(x)
  +
# "leftlimit" - returns lim_{x->a^-}f(x)
  +
# "rightlimit" - returns lim_{x->a^+}f(x)
  +
# "limit" - returns lim_{x->a}f(x) or "DNE"
  +
#
  +
# What does the applet do?
  +
# The applet draws a graph with jumps, a cusp and discontinuities
  +
# When turned on, there is context sensitive help.
  +
##############################################################################
  +
###################################
  +
# Create link to applet
  +
###################################
  +
$appletName = "Graph_Limit";
  +
$applet = FlashApplet(
  +
codebase => findAppletCodebase("$appletName.swf"),
  +
appletName => $appletName,
  +
appletId => $appletName,
  +
setStateAlias => 'setXML',
  +
getStateAlias => 'getXML',
  +
setConfigAlias => 'setConfig',
  +
maxInitializationAttempts => 10, # number of attempts to initialize applet
  +
#answerBoxAlias => 'answerBox',
  +
height => '475',
  +
width => '425',
  +
bgcolor => '#ffffff',
  +
debugMode => 0,
  +
submitActionScript => qq{
  +
getQE("inc").value=getApplet("$appletName").get_interval_info("increasing");
  +
getQE("dec").value=getApplet("$appletName").get_interval_info("decreasing");
  +
getQE("constant").value=getApplet("$appletName").get_interval_info("constant");
  +
},
 
);
 
);
  +
 
###################################
 
###################################
# Configure applet
+
# Configure applet
###################################
+
###################################
 
 
#initially the answers will be blank
 
  +
# configuration consists of hintState, question type, and random seed,
$applet->configuration(qq{<xml>
 
  +
# and x-coordinates of four points where jumps, discontinuities or cusps
<plot func='(1+2*x)*cos(x+x^2)'
 
  +
# occur.
lower='0' upper='$b'/>
 
  +
$applet->configuration(qq{<xml><hintState>$showHint</hintState><qtype>limits</qtype>
<grids xgrid='1' ygrid='$b'/>
 
  +
<seed>$problemSeed</seed><xlist x1='$x1' x2='$x2' x3='$x3' x4='$x4' /></xml>});
<win xmin='-3' xmax='$ubig'
 
  +
$applet->initialState(qq{<xml><hintState>$showHint</hintState><qtype>limits</qtype>
ymin='$vsmall' ymax='$vbig'
 
  +
<seed>$problemSeed</seed><xlist x1='$x1' x2='$x2' x3='$x3' x4='$x4' /></xml>});
umin='-3' umax='$ubig'
 
vmin='$vsmall' vmax='$vbig' />
 
<ans func='' lower='' upper =''
 
theValue='' />
 
<usub ufunc='x+x^2'/></xml>});
 
#initially the answers will be blank
 
$applet->initialState(qq{<xml>
 
<plot func='(1+2*x)*cos(x+x^2)'
 
lower='0' upper='$b'/>
 
<grids xgrid='1' ygrid='$b'/>
 
<win xmin='-3' xmax='$ubig'
 
ymin='$vsmall' ymax='$vbig'
 
umin='-3' umax='$ubig'
 
vmin='$vsmall' vmax='$vbig' />
 
<ans func='' lower='' upper =''
 
theValue='' />
 
<usub ufunc='x+x^2'/></xml>});
 
   
TEXT( MODES(TeX=>'object code',
+
TEXT( MODES(TeX=>'object code', HTML=>$applet->insertAll(
HTML=>$applet->insertAll(
 
 
debug=>0,
 
debug=>0,
includeAnswerBox=>1,
+
includeAnswerBox=>0,
  +
# reinitialize_button=>$permissionLevel>=10,
 
)));
 
)));
  +
  +
  +
BEGIN_TEXT
  +
<input type="hidden" name="inc" id="inc" />
  +
<input type="hidden" name="dec" id="dec" />
  +
<input type="hidden" name="constant" id="constant" />
  +
END_TEXT
  +
  +
$answerString1 = $inputs_ref->{inc};
  +
my $correctAnswer1 = List($answerString1);
  +
  +
$answerString2 = $inputs_ref->{dec};
  +
my $correctAnswer2 = List($answerString2);
  +
  +
$answerString3 = $inputs_ref->{constant};
  +
my $correctAnswer3 = List($answerString3);
  +
  +
 
</pre>
 
</pre>
| <p>
+
</td>
  +
<td style="background-color:#ccffff;padding:7px;">
  +
<p>
 
This is the <strong>Applet link section</strong> of the problem.
 
This is the <strong>Applet link section</strong> of the problem.
 
</p><br>
 
</p><br>
Line 171: Line 224:
 
Those portions of the code that begin the line with <code>#</code> are comments and can be omitted or replaced with comments appropriate to your particular problem.
 
Those portions of the code that begin the line with <code>#</code> are comments and can be omitted or replaced with comments appropriate to your particular problem.
 
</p>
 
</p>
<p>You must include the section that follows <code># Create link to applet</code>. If you are embedding a different applet, from the uSub applet, put your applet name in place of 'uSub' in the line <code>$appletName = "uSub";</code>. Enter the height of the applet in the line <code>height => '550',</code> in place of 550 and the width in the line <code>width => '700',</code> in place of 700.
+
<p>You must include the section that follows <code># Create link to applet</code>. If you are embedding a different applet, from the Graph_Limit applet, put your applet name in place of 'Graph_Limit' in the line <code>$appletName = "Graph_Limit";</code>. Enter the height of the applet in the line <code>height => '475',</code> in place of 475 and the width in the line <code>width => '425',</code> in place of 425.
 
</p><br>
 
</p><br>
<p> The lines <code>$applet-></code> <code>configuration(qq{<xml><plot func='(1+2*x)*cos(x+x^2)' </code> <code>lower='0' upper='$b'/></code> <code><br>
 
  +
<p> The lines <code>$applet->configuration(qq{<xml><hintState>$hintState</hintState><qtype>$qtype</qtype><seed>$problemSeed</seed><xlist x1='$x1' x2='$x2' x3='$x3' x4='$x4' /></xml>});</code> and <code>$applet->initialState(qq{<xml><hintState>$hintState</hintState><qtype>$qtype</qtype><seed>$problemSeed</seed><xlist x1='$x1' x2='$x2' x3='$x3' x4='$x4' /></xml>});</code> configure the applet. The configuration of the applet is done in xml. The hintState is set to the variable <code>$hintState</code>, the question type is set to <code>$qtype</code> and the problem seed is the WeBWorK environmental variable <code>$problemSeed</code>. The variables <code>$x1</code>, <code>$x2</code>, <code>$x3</code> and <code>$x4</code> are also passed to the applet.
<grids xgrid='1' ygrid='$b'/></code> <code><br>
 
  +
</p><br>
<win xmin='-3' xmax='$ubig' ymin='$vsmall' ymax='$vbig'
 
  +
<p>The code <code>qq{ </code><code>
umin='-3' umax='$ubig' vmin='$vsmall' vmax='$vbig' /></code> <code><br>
 
  +
getQE("inc").value=getApplet("$appletName").get_interval_info("increasing");</code><code>
<ans func='' lower='' upper ='' theValue='' /></code> <code><br>
 
  +
getQE("dec").value=getApplet("$appletName").get_interval_info("decreasing");</code><code>
<usub ufunc='x+x^2'/></xml>});</code>
 
  +
getQE("constant").value=getApplet("$appletName").get_interval_info("constant");</code><code>
<br>
 
  +
}</code>
and
 
  +
is called when the 'Submit Answers' button in the problem is pressed. There is an external interface function designed inside the applet. The function name is 'get_interval_info'. These lines of code call the function with javascript. <code>get_interval_info</code>, takes one argument: a string value. The string may be any of the following alternatives: "increasing", "decreasing", "constant", "up", "down" or "straight". <code>get_interval_info</code> returns a list of open intervals with the specified characteristic. The line <code>
<br>
 
  +
getQE("inc").value=getApplet("$appletName").get_interval_info("increasing");</code> gets the value of the function <code>get_interval_info</code> and stores this value in the hidden javascript form field named "inc". Note that although we have carriage returns after each of the 'getQE' statements, you should <em>not</em> have these carriage returns in your pg file. They are here so that the text line will allow display of the code next to the explanation. You will get error messages if you have the carriage returns in your pg file.</p>
<code>$applet-></code> <code>initialState(qq{<xml><plot func='(1+2*x)*cos(x+x^2)' </code> <code>lower='0' upper='$b'/></code> <code><br>
 
  +
<p>
<grids xgrid='1' ygrid='$b'/></code> <code><br>
 
  +
The hidden form fields are created in the code block:
<win xmin='-3' xmax='$ubig' ymin='$vsmall' ymax='$vbig'
 
  +
<code>
umin='-3' umax='$ubig' vmin='$vsmall' vmax='$vbig' /></code> <code><br>
 
  +
BEGIN_TEXT</code><code>
<ans func='' lower='' upper ='' theValue='' /></code> <code><br>
+
<input type="hidden" name="inc" id="inc" /></code><code>
<usub ufunc='x+x^2'/></xml>});</code>
+
<input type="hidden" name="dec" id="dec" /></code><code>
<br> configure the applet. The configuration of the applet is done in xml. The applet expects to be told the integrand of the original integral (func='(1+2*x)*cos(x+x^2)'), the lower limit of integration (lower='0'), the upper limit (upper='$b'), the horizontal and vertical grid spacing (xgrid='1' ygrid='$b'), the dimensions of the two graph windows (,code><win xmin='-3' xmax='$ubig' ymin='$vsmall' ymax='$vbig'
+
<input type="hidden" name="constant" id="constant" /></code><code>
umin='-3' umax='$ubig' vmin='$vsmall' vmax='$vbig' /></code>) and the u-substitution the student is to use (<code><usub ufunc='x+x^2'/></code>).
+
END_TEXT
  +
</code>
  +
</p><br>
  +
<p>
  +
The applet is configured in the code line:
  +
<code>$applet->configuration(qq{<xml><hintState>$hintState</hintState><qtype>limits</qtype>
  +
<seed>$problemSeed</seed><xlist x1='$x1' x2='$x2' x3='$x3' x4='$x4' /></xml>});</code> and the similar line below it.
  +
The variables $hintState, $problemSeed, and $x1, $x2, $x3, and $x4 are defined within WeBWorK and used by the applet to set the problem up.
 
</p><br>
 
</p><br>
<p>The code <code>qq{getQE("answerBox").value=getApplet("$appletName").getAnswer() }</code>
 
is called when the 'Submit Answers' button in the problem is pressed. This will call the getAnswer function which will return the contents of the four answer blanks in the applet.</p>
 
<br>
 
 
<p>
 
<p>
 
<code>TEXT( MODES(TeX=>'object code', HTML=>$applet->insertAll(
 
<code>TEXT( MODES(TeX=>'object code', HTML=>$applet->insertAll(
Line 203: Line 253:
 
<p>When the submit button is pressed, the hidden form fields defined in this block are filled with information from the applet.
 
<p>When the submit button is pressed, the hidden form fields defined in this block are filled with information from the applet.
 
</p>
 
</p>
|- style=" background-color:#ccffff;"
 
  +
<p>
| <pre>
 
  +
The data from the hidden form fields is used in these simple perl subroutines to define the correct answers to the four questions that are part of this WeBWorK problem.</p><br>
TEXT(MODES(TeX=>"", HTML=><<'END_TEXT'));
 
  +
<p>The WeBWorK variable $answerString1 is the content of the hidden form field "inc". $correctAnswer1 is the solution to the first question. The solutions for the next two questions are defined in a similar way.</p>
<script>
 
  +
</td>
if (navigator.appVersion.indexOf("MSIE") > 0) {
 
  +
</tr>
document.write("<div width='3in'
 
  +
<tr valign="top">
align='center' style='background:yellow'>
 
  +
<td style="background-color:#ffdddd;border:black 1px dashed;">
You seem to be using Internet Explorer.
 
  +
<pre>
<br/>It is recommended that another
 
browser be used to view this page.</div>");
 
}
 
</script>
 
END_TEXT
 
</pre>
 
| <p>
 
The text between the <code><script></code> tags detects whether the student is using Internet Explorer. If the student is using this browser, a warning is issued and the student is advised to use another browser. IE mis-sizes the applets. Some will work correctly when displayed at the wrong size, but others will fail. We do not recommend using IE with WeBWorK problems with Flash embedded.</p>
 
|- style="background-color:#ffdddd;"
 
| <pre>
 
 
BEGIN_TEXT
 
BEGIN_TEXT
   
 
$BR
 
$BR
$BR Complete the indicated blanks
 
in the applet. When done click
 
'submit answers'.
 
   
$PAR If you click 'submit answers'
 
  +
$BR list all intervals for which
before you are done, WeBWorK will
 
  +
$BR
save your work for when you log back on.
 
  +
a)
  +
\(f^\prime(x)>0\)
  +
\{ans_rule(35) \}
  +
$BR
  +
b)
  +
\(f^\prime(x)<0\)
  +
\{ans_rule(35) \}
  +
  +
$BR
  +
c)
  +
\(f^\prime(x)=0\)
  +
\{ans_rule(35) \}
  +
  +
$BR
   
 
END_TEXT
 
END_TEXT
 
Context()->normalStrings;
 
Context()->normalStrings;
 
</pre>
 
</pre>
| <p>
 
  +
<td style="background-color:#ffcccc;padding:7px;">
  +
<p>
 
This is the <strong>text section</strong> of the problem. The <code>TEXT(beginproblem());</code> line displays a header for the problem, and the <code>Context()-&gt;texStrings</code> line sets how formulas are displayed in the text, and we reset this after the text section. Everything between the <code>BEGIN_TEXT</code> and <code>END_TEXT</code> lines (each of which must appear alone on a line) is shown to the student.
 
This is the <strong>text section</strong> of the problem. The <code>TEXT(beginproblem());</code> line displays a header for the problem, and the <code>Context()-&gt;texStrings</code> line sets how formulas are displayed in the text, and we reset this after the text section. Everything between the <code>BEGIN_TEXT</code> and <code>END_TEXT</code> lines (each of which must appear alone on a line) is shown to the student.
 
</p>
 
</p>
 
<p>
 
<p>
Answers are submitted within the applet, so no answer blanks are provided here. The parser in the applet is not as sophisticated as the WeBWorK parser so '*' must explicitly be entered for times in order for the function to graph within the applet. The answers are graded by WeBWorK so a correctly formulated WeBWorK answer will be marked as correct, but may not be graphable.
 
  +
Mathematical equations are delimited by <code class="tex2math_ignore">\( \)</code> (for inline equations) or <code class="tex2math_ignore">\[ \]</code> (for displayed equations); in these contexts inserted text is assumed to be TeX code.
 
</p>
 
</p>
|- style="background-color:#eeddff;"
 
  +
<p>
| <pre>
 
  +
There are a number of variables that set formatting: <code>$PAR</code> is a paragraph break (like <code>\par</code> in TeX).
###################################
 
  +
[[FormatVariableList|This page]] gives a list of variables like this. Finally, <code>\{&nbsp;\}</code> sets off <em>code that will be executed in the problem text</em>. Here, <code>ans_rule(35)</code> is a function that inserts an answer blank 35 characters wide.
  +
</p>
  +
</td>
  +
</tr>
  +
<tr valign="top">
  +
<td style="background-color:#eeddff;border:black 1px dashed;">
  +
<pre>
  +
##############################################################
 
#
 
#
 
# Answers
 
# Answers
Line 249: Line 307:
 
## answer evaluators
 
## answer evaluators
   
NAMED_ANS( 'answerBox'=>$anslist->
 
  +
ANS( $correctAnswer1->cmp(strings=>['None']) ); #checks AnSwEr00001
cmp(ordered=>1) );
 
  +
ANS( $correctAnswer2->cmp(strings=>['None']) ); #checks AnSwEr00002
  +
ANS( $correctAnswer3->cmp(strings=>['None']) ); #checks AnSwEr00003
   
ENDDOCUMENT();
 
  +
  +
ENDDOCUMENT();
 
</pre>
 
</pre>
| <p>
 
  +
<td style="background-color:#eeccff;padding:7px;">
This is the <strong>answer</strong> section of the problem. The problem answer is recorded in the applet. The code <code>NAMED_ANS( 'answerBox'=>$anslist->cmp(ordered=>1) );</code> compares the answer entered into the applet (the contents of 'answerBox') with the WeBWorK variable <code>$anslist</code>. The answer is graded as an ordered list.
 
  +
<p>
  +
This is the <strong>answer</strong> section of the problem. The problem answer is set by the <code>ANS( $correctAnswer1->cmp(strings=>['None']) );</code>, <code>ANS( $correctAnswer2->cmp(strings=>['None']) );</code>, <code>ANS( $correctAnswer3->cmp(strings=>['None']) );</code> lines. These compare the student's answer with the answers returned from the applet. The answers allow for either a list of intervals answer or the string 'None' for empty lists.
  +
</p>
  +
<p>
  +
The solution is embedded in the applet and becomes available when the due date has passed.
 
</p>
 
</p>
 
<p>
 
<p>
 
The <code>ENDDOCUMENT();</code> command is the last command in the file.
 
The <code>ENDDOCUMENT();</code> command is the last command in the file.
 
</p>
 
</p>
|}
 
  +
</td>
 
  +
</tr>
== License ==
 
  +
</table>
 
The Flash applets developed under DUE-0941388 are protected under the following license:
 
[http://creativecommons.org/licenses/by-nc/3.0/ Creative Commons Attribution-NonCommercial 3.0 Unported License].
 
 
   
 
[[Category:Sample Problems]]
 
[[Category:Sample Problems]]
 
[[Category:Applets]]
 
[[Category:Applets]]
[[Category:Flash Applets]]
 
 
[[Category:Problem_Techniques]]
 
[[Category:Problem_Techniques]]

Please note that all contributions to WeBWorK_wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see The WeBWorK Project wiki:Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)