## Forum archive 2000-2006

### Zbigniew Fiedorowicz - Moodle-WeBWorK for gateway testing

by Arnold Pizer -
Number of replies: 0
 Moodle-WeBWorK for gateway testing topic started 3/4/2003; 11:30:01 AMlast post 3/5/2003; 10:10:46 AM
 Zbigniew Fiedorowicz - Moodle-WeBWorK for gateway testing  3/4/2003; 11:30:01 AM (reads: 1199, responses: 2) I just realized that my interface with Moodle canbe used to implement the use of WeBWorK for gatewaytesting.Here's how it would work. The crucial element wouldbe a WeBWorK course into which students are NOT allowedto log in. Their WeBWorK passwords would be kept topsecret. The only way they could access the problemassignments in the course would be via Moodle.First of all the gateway tests would be prebuilt inthe WeBWorK course as regular WeBWorK homework assignments.When the student clicks on the link to the gateway testin Moodle, the URL would specify the actual due date forthe test and the time allowed for the test. The targetscript for this URL (a slight variant of the currentmoodle2wwk.pl script), would reset the random numberseeds on all the problems and set the due date totimenow + timeallowed. [All the sensitive data willbe verified by an MD5 checksum with a shared passwordbetween Moodle and the interface script.] Then thescript will call WeBWorK to display problem 1 of thetest. As currently the output from WeBWorK will befiltered by a wrapper script which will screen outany responses from WeBWorK about the (in)correctness ofthe student's answers. The wrapper script will alsoadd a timer display somewhere on the page, indicatinghow much time is remaining. When the student clicksthe submit button, the wrapper script will automaticallydisplay the next page. However the previous button willstill be available so the student can go back and fixan answer they may realize is wrong. The wrapper script will also display a button titled"Score this Quiz". When the student clicks on this,the total score for the quiz will be displayed. Atthe same time the due date in WeBWorK will be set tosome time in the past, so now the set will be deemedby WeBWorK to be past due. At the same time the scriptwill report the score back to Moodle. The studentwill also be given the option of going back to Moodleor going over the problem set once again, this timewith another wrapper script which will allow showingcorrect answers. This time instead of a Score the Quizbutton, there will be a Return to Moodle button.One can also allow for limited or unlimited retakes byencoding such information in the original URL and thepast due date that is set in WeBWorK after the quiz istaken and also in the hidden variables in the form.Again the sensitive hidden variables in the form canbe protected from tampering by cheating students viaMD5 checksums.Unless I've overlooked something, all this can beaccomplished via relatively modest modifications inmy existing scripts.Zig <| Post or View Comments |>

 Gavin LaRose - Re: Moodle-WeBWorK for gateway testing  3/5/2003; 9:06:53 AM (reads: 1480, responses: 0) Hi Zig, This is very cunning. I have a couple of questions, mostly to do with the administrative side of things. The way I'm reading this, every possible gateway test would be a different webwork assignment. Is this right? Given the ability to reset the seed the student uses for any given assignment, this isn't necessarily an issue. However, for comparison, we're currently doing a derivative gateway which is generated with seven topics, each drawn from a bank of about 100 questions---at face value this could be a lot of assignments. Of course, the more relevant question is how many times students take the test. I'd have to check to be sure, but I think the upper bound for us is probably over 20 and less than 40. Following this line of thought, I assume that the Moodle script would randomly select which of the gateway assignments was returned to the student. Does Moodle allow the easy aggregation of the results of the different tests (webwork assignments) too? In particular, most instructors are going to want a list of the students in their class with an indication of whether or not they passed the gateway test. And then the ability to go and look at the tests that each of the students took. I hope those make sense. I haven't had any coffee yet this morning and it's starting to seem that might be to my detriment. Thanks, Gavin <| Post or View Comments |>

 Zbigniew Fiedorowicz - Re: Moodle-WeBWorK for gateway testing  3/5/2003; 10:10:46 AM (reads: 1424, responses: 0) > * The way I'm reading this, every possible gateway test would be a different> webwork assignment. Is this right? Given the ability to reset the seed the> student uses for any given assignment, this isn't necessarily an issue.> However, for comparison, we're currently doing a derivative gateway which is> generated with seven topics, each drawn from a bank of about 100> questions---at face value this could be a lot of assignments. Of course, the> more relevant question is how many times students take the test. I'd have to> check to be sure, but I think the upper bound for us is probably over 20 and> less than 40.Not necessarily. A lot of variation can be encoded into the WeBWorK problemsthemselves. Eg. depending on the seed, present one of five problems allencoded within one WeBWorK problem. Also it might be possible to write amacro or perhaps modify dangerousMacros.pl to read in another random problemfrom within a given a given WeBWorK problem. Prior to v. 1.8, one would runinto the problem of the need to cache Latex2Html generated images, but nowwith the much faster dvipng, this issue has now largely vanished.> * Does Moodle allow the easy aggregation of the results of the different> tests (webwork assignments) too? In particular, most instructors are going> to want a list of the students in their class with an indication of whether> or not they passed the gateway test. And then the ability to go and look at> the tests that each of the students took.I am not exactly sure what you mean by aggregation. The way I currentlyenvision my scheme: the instructor could specify the following informationin the setup to the quiz: passing grade for the gateway, time allowedfor each attempt, maximum number of attempts, due date after which nofurther attempts are allowed. The interface would return to Moodle thefollowing information: the score on the last attempt and how manyattempts were made so far. The instructor would need to log into theWeBWorK course to see the last version of the gateway that the studenttook.Zig <| Post or View Comments |>