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

Ensure comprehensive cost values are being derived from ATD death count #4017

Closed
JaceDeloney opened this issue Sep 23, 2020 · 6 comments · Fixed by cityofaustin/vision-zero#938
Assignees
Labels
Product: Vision Zero Crash Data System Centralize the management of ATD's Vision Zero data Service: Dev Infrastructure and engineering Workgroup: VZ Vision Zero Program
Milestone

Comments

@JaceDeloney
Copy link

JaceDeloney commented Sep 23, 2020

Lewis found a crash id that apparently isn't using the correct values for comprehensive cost, economic cost, and speed management points. The correct values per ATD fatality (person count) should be:

  • $2,829,000 for comp cost
  • $1,679,600 for economic cost
  • 10 points for speed management

We need to determine what is causing the issue with this specific crash ID, and then determine if this issue is affecting other crashes as well.

@JaceDeloney JaceDeloney added Product: Vision Zero Crash Data System Centralize the management of ATD's Vision Zero data Service: Dev Infrastructure and engineering Workgroup: VZ Vision Zero Program labels Sep 23, 2020
@JaceDeloney JaceDeloney added this to the Sprint 35 milestone Sep 23, 2020
@JaceDeloney JaceDeloney modified the milestones: Sprint 35, Sprint 34 Sep 23, 2020
@tillyw
Copy link

tillyw commented Oct 5, 2020

@JaceDeloney, I'm investigating this with guidance from @sergiogcx. I think the values per fatality are correct in VZE, so the problem may lie elsewhere.

Should est comp cost take into account unknown injury count? Prod does not currently factor that in. If so, that may be the issue, at least for est comp cost.

If you're able to provide me with the correct totals we should be displaying, I may be able to figure out where the discrepancy is coming from and how to solve it.

@tillyw
Copy link

tillyw commented Oct 6, 2020

Current triggers in prod:

NEW.est_comp_cost = (0
   + (NEW.apd_confirmed_death_count * (estCompCostList[2]))
   + (NEW.sus_serious_injry_cnt * (estCompCostList[3]))
   + (NEW.nonincap_injry_cnt * (estCompCostList[4]))
   + (NEW.poss_injry_cnt * (estCompCostList[5]))
   + (NEW.non_injry_cnt * (estCompCostList[6]))

)::decimal(10,2);

NEW.est_econ_cost = (0
   + (NEW.apd_confirmed_death_count * (estCompEconList[2]))
   + (NEW.sus_serious_injry_cnt * (estCompEconList[3]))
   + (NEW.nonincap_injry_cnt * (estCompEconList[4]))
   + (NEW.poss_injry_cnt * (estCompEconList[5]))
   + (NEW.non_injry_cnt * (estCompEconList[6]))

)::decimal(10,2);

NEW.speed_mgmt_points = (0
	+ (NEW.apd_confirmed_death_count * (speedMgmtList [2]))
    + (NEW.sus_serious_injry_cnt * (speedMgmtList [3]))
    + (NEW.nonincap_injry_cnt * (speedMgmtList [4]))
    + (NEW.poss_injry_cnt * (speedMgmtList [5]))
    + (NEW.non_injry_cnt * (speedMgmtList [6]))
)::decimal (10,2);

@JaceDeloney
Copy link
Author

Action items from sprint review:

  • change to ATD confirmed
  • Add unknown injury severity category

@tillyw
Copy link

tillyw commented Oct 6, 2020

Unknown injury should be counted at $51,000 per person count

@JaceDeloney
Copy link
Author

Screen Shot 2020-10-06 at 11 05 41 AM

@sergiogcx
Copy link

This is the PR associated to this issue: cityofaustin/vision-zero#938

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product: Vision Zero Crash Data System Centralize the management of ATD's Vision Zero data Service: Dev Infrastructure and engineering Workgroup: VZ Vision Zero Program
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants