RE: [Aimmath-developers] AiM 3.0 will support Maple versions 7, 8, and 9

[Ken M. <mo...@pt...>]

> -----Original Message-----
> From: aim...@li...
> [mailto:aim...@li...]On Behalf Of
> Gustav W Delius
> Sent: Saturday, August 23, 2003 6:11 AM
> To: AIM developers
> Subject: [Aimmath-developers] AiM 3.0 will support Maple versions 7, 8,
> and 9
>
>
> As far as I am aware there is no one out there who has expressed an
interest
> in using AiM 3.0 with Maple 6 or lower. So AiM 3.0 will support only Maple
> versions 7,8, and 9.
>
> I can't test AiM under Maple 9 but I gather from the posts on this list
that
> all problems have been resolved and the code currently in CVS works with
> Maple 9. Is that correct?

I am currently using the develop_2_1 version of AIM under Maple 9 and after
tweaking the code in a few places (already committed) it seems to be working
fine with one exception. I am getting a very weird sporadic error for
certain questions when I Try (as administrator) a quiz.  Namely, the
teacher's answer that is provided automatically by AIM in the answer box for
certain questions when Trying a quiz is sometimes marked as being invalid
with errors like:

"Your answer contains a forbidden name: x."

Sometimes the variable is "k", or "m" or "x" depending on what the question
selects for the variable and which question it is but it is usually a single
letter variable.  The odd part of this is that if I try the same question
separately, and use the exact same AIM-supplied answer, it marks it correct
with no problems.  In fact, I can mark the question as many times as I like
if I Try it separately or if I try it as a student in a quiz, and it works
flawlessly, but when I Try the whole quiz I get the validation error.  It is
not repeatable either.  If I Try the quiz a second time the same question
might work, but some other questions in the same quiz might have the
validation error.

I have tried to reproduce this behavior in Maple 8, but it never happens, so
I think this is something new to Maple 9.  My guess is that there is some
new twist in the internal way that Maple stores things that is throwing off
the use of disassemble() in SafeParse, but the sporadic nature of the
problem is making that really hard to track down.

Does anyone have any idea about what might be causing it?

Other than this it seems to work fine in Maple 9 as far as I've tested it.

KEN