Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: Possible error in number exercise. #131

Open
RTBagamoyo opened this issue Feb 27, 2023 · 2 comments
Open

Bug report: Possible error in number exercise. #131

RTBagamoyo opened this issue Feb 27, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@RTBagamoyo
Copy link
Collaborator

RTBagamoyo commented Feb 27, 2023

Tablet number: 6111000852
RT version: 3.2.2.1
Date: 2023/02/20
Time: 09.09

The exercise on the picture below might have a STUCK bug. It never responds to taps and doesn't really do anything, other than showing the screen that is shown on the picture.
Is this on purpose? I think that the kids are supposed to press the amount of dots similar to the number above, but the dots are already there when the activity starts.

image

@RTBagamoyo RTBagamoyo added the bug Something isn't working label Feb 27, 2023
@JackMostow
Copy link
Contributor

The "numcompare" in the activity name means the task is to tap on the smaller of the two numbers. The prompt at the start of the activity should say so; does it? The two numbers are displayed both as numerals (4, 1) and as quantities (...., .), which is why the dots are already there. The purpose of this task is to develop number sense at a stage where children are still learning to associate numerals, quantities, and spoken numbers. Please check if tapping on the numeral works.

Tapping on a non-target indicates that the child does not understand the task, so it should make RoboTutor respond accordingly, e.g. by repeating the prompt. We have but do not yet use code to detect taps on non-targets.

@JackMostow
Copy link
Contributor

A next step is to inspect the log around the time of the bug, but it hasn't been uploaded yet, judging from Bagamoyo_2023-02-14..2023-02-21_RoboTutor_usage_weekly_report, which lists 2023-02-16 as the latest session date, well before the February 20th, 09.09am bug report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants