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

Assignment count < Completion count in the street edge assignment table #1135

Closed
manaswisaha opened this issue Oct 9, 2017 · 6 comments
Closed

Comments

@manaswisaha
Copy link
Member

manaswisaha commented Oct 9, 2017

The assignment count is less than the completion count for a street edge. This should not be the case. I don't think it has dire consequences but this should be investigated and fixed.

Example regions to check are 204 and 205. Here is the screenshot showing a sample of that (in region 205):

image
3rd column is the assignment count and 4th is the completion count.

Query used to generate this: select * from street_edge_assignment_count where street_edge_id IN (select street_edge_id from street_edge_region where region_id = 204);

@manaswisaha manaswisaha added the Bug label Oct 9, 2017
@jonfroehlich
Copy link
Member

jonfroehlich commented Oct 9, 2017 via email

@manaswisaha
Copy link
Member Author

Assignment count is the number of times a street has been assigned to users for auditing. They might not audit it, so that would result into 0 completion count for those, but any street that is assigned for auditing should have an assignment count of at least 1.

So it seems wrong to have streets that have >0 completion count but 0 assignment count.

So to investigate this we have to confirm whether the code is based on this logic or not. Intuitively, this should be the logic. This old code has not been modified since the very beginning, hence bugs (if they were present from the very beginning) didn't surface before now since we are actively using this table to assign least audited routes using the completion count column. To my knowledge, we don't use assignment count for anything significant yet.

@jonfroehlich
Copy link
Member

jonfroehlich commented Oct 9, 2017 via email

@misaugstad
Copy link
Member

possible bug fix for @Adash12 to work on?

@misaugstad
Copy link
Member

I actually don't think that we use assignment and completion count directly anymore. We now base our street priority on the "good user audit count", so I don't think this table really has a use, except to as a pre-computed value that we look at on the admin page. However, this isn't the most time-consuming thing to compute, so I think we could just delete this table entirely.

@misaugstad
Copy link
Member

We opted to just remove this table. Closing via #1328

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants