-
Notifications
You must be signed in to change notification settings - Fork 14
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
Already_seen banner appearing too frequently #288
Comments
linked to #289 That issue says: All subjects are marked with already seen banners once the first 4/5 subjects are classified. This only impacts on workflows with configuration directive Noting that i've checked the selection APIs and they aren't returning seen images in any subject requests. I was using Zooniverse App v2.6.2
|
@lcjohnso Thanks for the heads up. I believe they could still erroneously see the "Already Seen" banner, regardless of the The other issue they bring up in their ticket is a separate bug that we have dealt with recently, but a new issue should be drawn up to address it. |
I've had reports of this happening on fast workflows for science scribbler, https://www.zooniverse.org/projects/msbrhonclif/science-scribbler/talk/1147/1428346?comment=2321278&page=1 I looked into the users and they have a lot of data remaining to classify on these workflows. I requested the user try the desktop app (so hitting the same selector services) but different client side handling of the incoming set of subjects. They saw no seen banners on the PFE client but did on the mobile client. If we're going to continue to launch mobile workflows we have to spend some time investigating this to avoid wasting volunteer effort. |
Perhaps also related: #287 |
Per Oct 24 Slack convo.
There may be an issue with how often the already seen banner is showing up and also how subjects are added to the queue.
After saving a classification, it looks like a subject is marked already_seen in the subjectList here -
mobile/src/reducers/classifierReducer.js
Line 74 in f975481
And then, the first subject that isn’t marked already_seen is grabbed here and made the next subject -
mobile/src/reducers/classifierReducer.js
Line 100 in f975481
But, if all subjects are marked already_seen in the above line, a random subject from the list is grabbed, which has probably already been seen. That might explain why already seen subjects are seen too frequently.
Later, if there are less than five subjects in the list that haven’t been seen, new subjects are grabbed here from the /queued route. However, those subjects are tacked on to the existing list without changing the fact that the current one might’ve already been seen -
mobile/src/actions/classifier.js
Line 114 in a8ca98f
I think the solution would be to get new subjects from the queued route here instead of a random subject
mobile/src/reducers/classifierReducer.js
Line 104 in f975481
The text was updated successfully, but these errors were encountered: