I created this activity during the workshop, but I have since made significant changes to it. One area I struggled with was restricting answers to a particular format.
If anyone has time to review my activity, I would appreciate your feedback, suggestions, or identification of any mistakes that I may have missed.
I originally used a cascade structure, but for easier reading and navigation, I changed it to “Reveal All.”
Any feedback is greatly appreciated. Thank you!
Activity link below:
Nice work! I’m assuming that you plan to remove the revealAll before giving it to students. With that assumptions, I won’t worry about cases where a section gives away the answer of a previous section since it won’t be visible until the previous section is correct.
Regarding restricting answers to a particular format, I imagine that first case where that is a concern is for Step 4. If you want the answer to accept (x+3)^2 and nothing else, you can add the attribute symbolicEquality to the <answer> or to the <award>. If you want it also accept answers like (3+x)^2 and (x+1+1+1)^2 but not x^2+6x+9, then you can keep the attribute symbolicEquality and add the second attribute simplifyOnCompare="full".
If you don’t supply symbolicEquality, then by default, Doenet uses a numeric answer checker that will accept any answer that it can determine is mathematically equivalent to the correct answer. If you specify symbolicEquality by itself, then the answer-checking becomes very strict. That’s why relaxing symbolicEquality with simplifyOnCompare is often useful.
Duane
My thoughts: Step 2; make the length ‘3’ much shorter than ‘x’ in the picture. The new rectangles should be quite a bit different than squares.
I like the first question as to WHY we are doing this. It builds a visual understanding.
Also in the second question, add a word… ‘What are the side lengths of each NEW rectangle.’
Step 3 is great.
I also like Steps 4 and 5 and like where Step 6 is headed. That’s all the time I had to review.
Thank you Duane. During the workshop, we talked about the when component, and without fully realizing its intended purpose, I think I started using it everywhere. When you pointed out Step 4, I went back and reviewed the activity. That is when I realized I had been using the same approach from Steps 1 through 7. I changed it now. Thank you for pointing that out. I appreciate the feedback and the help.
Thank you, Mike, for your suggestions. I incorporated both of your recommendations into my activity. Thank you again for your feedback. I truly appreciate your help and guidance.