Hi all,
I've discovered an issue where the Samigo Tests & Quizzes Calculated Question type can mark correct answers as incorrect. The situation is the following:
Here's an example question:
Question Text: {x}^2 = {{y}}
x is any number between 500000 and 1000000, with 2 decimal places
Tolerance is default for the question type: 0.01
Decimal places for answer: 3
One instance of this question that comes up for an example
student is: 871542.68^2 = ___
The answer provided by my TI-83 calculator (which also has a
scientific notation conversion threshold of 1E11) is 7.595866431E11,
but if I type this directly into the answer box, Samigo counts it
incorrect and gives me 7.596E11 for the correct
answer.
Similarly, 759586643061 is counted as incorrect (it SHOULD
be the correct answer), but 759600000000 is marked
correct.
As expected, tolerance applies to the true number Samigo calculates for the answer (ignoring scientific notation).
In the case of the question above, the 0.01 tolerance applies to
759600000000.00. Samigo would mark any value between
759599999999.99 and 759600000000.01 as correct. Thus, for
this question, I would need to set a MASSIVE tolerance (in the
millions) to make Samigo count my calculator's correct answer as
correct. If I did that, a student entering any value in a range
of several million would get the question marked correct.
So the question is: how should Samigo behave when a LARGE number
for the Answer is converted to scientific notation? I
assume it should do the following:
If my assumption is correct, I'll create a bug jira with this information; if not, please let me know what should be the correct behavior!
Thanks,
Tiffany
--
You received this message because you are subscribed to the Google Groups "Sakai Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-user+...@apereo.org.
To post to this group, send email to sakai...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-user/.
Hi Shawn and Matthew,
Unfortunately, I don't think the issues in the jiras you mentioned below will help with this because it looks like those are fixed in 12 and this issue is present everywhere I've tested. I apologize for not including this information in my original message - I tested on the following servers: